This is the mail archive of the
mailing list for the GDB project.
Re: RFA: Using year ranges in copyright notices...
> > +Such ranges are used when nontrivial changes were made to that file
> > +each and every year in the range (inclusive).
> The FSF rule for listing a year is "nontrivial changes to the package"
> rather than "to that file" (this is the basis on which it's OK to update
> the year in all files at the start of the year). As I understand it, this
> combines with the rule about ranges to allow "<first-year>-2012" for every
> file (at least, if there is some version in version control from each year
> in the range).
That's a good point, thank you.
I propose we simply remove that sentence, then. It's not really
all that necessary, after all. Here is a new revision.
Author: Joel Brobecker <firstname.lastname@example.org>
Date: Tue Jan 3 12:41:50 2012 +0400
[README] Add not about copyright and license notices
Also explain the use of year ranges in copyright notices.
* README (Copyright and License Notices): New section.
diff --git a/gdb/README b/gdb/README
index d79fecc..7ffe90a 100644
@@ -638,6 +638,26 @@ testsuite `standalone', without it being part of the GDB source tree.
See the DejaGNU documentation for further details.
+Copyright and License Notices
+Most files maintained by the GDB Project contain a copyright notice
+as well as a license notice, usually at the start of the file.
+To reduce the length of copyright notices, consecutive years in the
+copyright notice can be combined into a single range. For instance,
+the following list of copyright years...
+ 1986, 1988, 1989, 1991-1993, 1999, 2000, 2007, 2008, 2009, 2010, 2011
+... is abbreviated into:
+ 1986, 1988-1989, 1991-1993, 1999-2000, 2007-2011
+Such ranges are used when nontrivial changes were made to that file
+each and every year in the range (inclusive).
(this is for editing this file with GNU emacs)