Top Level GCC change questions

Mike Stump mikestump@comcast.net
Thu Sep 20 19:59:00 GMT 2012


On Sep 20, 2012, at 12:01 AM, Georg-Johann Lay <gjl@gcc.gnu.org> wrote:
> Steve Ellcey schrieb:
>> DJ Delorie wrote:
>>>> Is there any automation for this or is it still up to each person
>>>> checking in files to copy stuff over by hand?
>>> There is no automation, as neither project was willing to cede control
>>> to the other.  In general, any patch applied to one repo should be
>>> (and may be) applied to the other, but at the moment it's up to each
>>> committer to actually do it.
>> OK.  I also noticed a change that is in the config directory in GCC
>> but not in binutils: [...]
> 
> There are also these two changes to configure[.ac]
> 
> http://gcc.gnu.org/viewcvs?view=revision&revision=190967
> http://gcc.gnu.org/viewcvs?view=revision&revision=190887
> 
> I filed a copyright assignment for the GCC project, so
> I don't know if it is appropriate to sync these changes
> with other FSF projects where I did not file a copyright assignment.

If you have paper work for gcc, gcc can accept them.  Once gcc accepts them, _anyone_ can move them from the gcc project to any other FSF project, provided the copyright is the same and the file is copyright FSF.  If the copyright is different in owner or in license (exclusions, GPL 2/3 or anything else), the case is less trivial and ask about the more complex cases.  You can double check, but I believe the files in question fit the trivial case.  One reason why the FSF insists on paperwork is to give it the latitude to do operations like this.



More information about the Gcc-patches mailing list