This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] README: Define what a copyright year range means.
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Carlos O'Donell <carlos at codesourcery dot com>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 20 Oct 2011 12:32:29 -0700 (PDT)
- Subject: Re: [PATCH] README: Define what a copyright year range means.
- References: <4EA0761E.2060007@codesourcery.com>
> GLIBC uses year range notation for copyright years.
It mostly does not, since that's what the FSF told me to do eons ago.
> There is nothing wrong with using ranges, but
> we should adjust the README to mention them.
>
> `6.5 Copyright Notices' says:
> ~~~
> You can use a range (2008-2010) instead of listing individual years (2008, 2009, 2010) if and only if: 1) every year in the range, inclusive, really is a copyrightable year that would be listed individually; and 2) you make an explicit statement in a README file about this usage.
> ~~~
> http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
Given that, I guess using ranges is OK now.
> +these additional notices to be distributed. License copyright years may be
Two spaces after a sentence.
> +listed using range notation e.g. 2000-2011, indicating that every year in
comma for e.g.
Thanks,
Roland