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] memset: also update copyright years


On Mon, Apr 9, 2012 at 9:14 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
>> In the case of glibc we *could* add copyright years to all the files
>> for every copyrightable year, but we don't
>
> I think I see part of the problem. ?glibc is transitioning from the old
> system (where every file kept track of the years *that file* was was
> published with a nontrivial change) to the new system (where every
> file keeps track of the years that the glibc package, a collective
> work, was published with a nontrivial change). ?Your sentence is referring
> to the old system. ?The GNU coding standards assume the new system,
> not the old.

Very good point.

> To clarify this, perhaps add the following text to maintain.texi?
> ?If a package's files use the older GNU style of copyright notices
> ?where every file's year lists were recorded independently, you can
> ?convert the copyright notices to the new style all at once, or you can
> ?convert each file's notices when the file is changed, whichever is
> ?more convenient.

"new style"=>"current style"

+ "Ensure that care is taken when converting between package file years
and copyrightable package years since they may not be the same, thus
preventing the merging of those years."

Which, if I understand everything correctly, is exactly the problem we
have in glibc.

Our first copyrightable package year was 1991.

We have some files with copyright years for 1990.

We can't merge 1990 into the range when we update the file.

Cheers,
Carlos.


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