This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Update copyright year after my most recent changes.


On Thu, 8 Mar 2012, Pedro Alves wrote:

> Any reason you don't do the same?

One contributor said they had a use for the existing date information in 
<http://sourceware.org/ml/libc-alpha/2012-01/msg00190.html>.  Since they 
did not follow up when asked for more details, I don't think that's 
actually relevant; such objections to changes are only admissible when the 
person making objections gives sufficient explanations and is willing to 
engage in discussions seeking a solution satisfying all parties.  So I 
think we should go ahead with using automatic updates at the start of the 
year, for both libc and ports.  Note:

* Automatic updates must not be used on files that are imported, 
unmodified, from other projects.

* For files that aren't currently imported unmodified but where it might 
be desirable to keep them in sync with other projects - subject to changes 
from those projects remaining available under glibc's license - it's not 
clear automatic updates are useful (but they probably aren't harmful 
either).  This covers files from GMP, gettext, libidn at least.

* Where generated files are involved, they should be regenerated after the 
automatic update rather than being directly automatically updated 
themselves.  I had to remove some changes from Paul Eggert's FSF address 
patch (bug 13673) because it didn't appear to deal with those files 
correctly.

* For soft-fp and longlong.h, we may not be able to make automatic updates 
to use ranges until GCC has the README notice explaining what ranges mean, 
since those files are also used in GCC.

* For conversions to ranges, years 1990 and earlier that are not 
explicitly listed cannot be included implicitly in a range.  So most files 
can use a single range, but maybe a few need to list earlier years 
separately.

* Automatic updates should only apply to copyright notices in the name of 
the FSF, not any other copyright holders.

-- 
Joseph S. Myers
joseph@codesourcery.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]