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 1:21 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 04/09/2012 10:15 AM, Carlos O'Donell wrote:
>
>> The FSF has said this is OK.
>> http://sourceware.org/ml/libc-alpha/2012-02/msg00125.html
>>
>> The GNU coding standards document has not yet been updated to reflect this.
>> http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
>
> As far as I can tell, the GNU coding standards have been updated accordingly:
> that is, they say that ranges are OK if there's a README comment to that effect,
> and they say that the years are for the package, not just for the individual file.
>
> If the coding standards' language is confusing please let me know where the
> confusion comes from, and perhaps we can clarify the standards.

It's not clear to *me* from the GNU coding standard when it is correct
and not correct to collapse the years.

I think that the piece of missing text is that which was provided by
Karl Berry in his email:
http://lists.gnu.org/archive/html/bug-standards/2012-02/msg00003.html

Now, your answer to "when can we collapse years" might be "it depends"
in which case the standard is fine and remains as a descriptive
standard, rather than proscriptive. It is then up to each package to
ask the FSF to rule under which conditions it is correct or not
correct to merge years.

Does that make sense?

Cheers,
Carlos.


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