This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Allow use of ranges in copyright notices
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Robert Dewar <dewar at adacore dot com>
- Cc: Alexandre Oliva <aoliva at redhat dot com>, David Edelsohn <dje dot gcc at gmail dot com>, <gcc at gcc dot gnu dot org>, <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 2 Jul 2012 14:17:25 +0000
- Subject: Re: Allow use of ranges in copyright notices
- References: <Pine.LNX.4.64.1206301449240.28133@digraph.polyomino.org.uk> <CAGWvny=CjjKyURf9ngxPHsjZswFV2B=kJ__W6465uLmCzgEUgA@mail.gmail.com> <ory5n2l4rv.fsf@livre.localdomain> <4FF1A55F.1030701@adacore.com>
On Mon, 2 Jul 2012, Robert Dewar wrote:
> On 7/2/2012 8:35 AM, Alexandre Oliva wrote:
> > On Jun 30, 2012, David Edelsohn <dje.gcc@gmail.com> wrote:
> >
> > > IBM's policy specifies a comma:
> >
> > > <first year>, <last year>
> >
> > > and not a dash range.
> >
> > But this notation already means something else in our source tree.
>
> I think using the dash is preferable, and is a VERY widely used
> notation, used by all major software companies I deal with!
And as a GNU project there isn't a choice between using IBM convention and
GNU convention - only about which of the GNU options we use. The simplest
is <first-year>-2012 (for any value of <first-year> 1987 or later) and so
I am proposing we move to that (make this change to README to allow it,
allow converting files when 2012 is added to the copyright years, as is
now done in glibc, allow a bulk conversion if anyone wishes to do one).
--
Joseph S. Myers
joseph@codesourcery.com