On Mon, Jun 07, 2021 at 02:17:55PM +0000, Giacomo Tesio wrote:
> Anyway, to most people it's just a matter of risk assesment.
>
> GCC will now come with a new legal risk that was absemt before, thus
> it should be handled properly, with a proper notice and incapaulated
> in a new major version.
>
> And tbh, it doesn't look such an unreasonable request, after all.
Nonsense. GCC codebase doesn't have a single copyright holder for
decades, just look at the source.
libffi has various copyright holders
include/hsa* has AMD as copyright holder
gcc/go/gofrontend and libgo has The Go Authors as copyright holders
liboffloadmic has mostly Intel as copyright holder
libphobos has mostly Digital Mars (and/or the D Language foundation) as
copyright holder
libquadmath has Sun Microsystems as copyright holder on various parts
libsanitizer has mostly the LLVM authors as copyright holders
zlib has various copyright holders
You can look at contrib/update-copyright.py, there you'll find a huge list
of various exceptions, external authors etc.
So, a few extra copyright holders under DCO instead of assignment to FSF
will not really change anything significant.
Jakub
