Allow use of ranges in copyright notices

[Joseph S. Myers]

I propose that GCC should allow the use of ranges of years (e.g. 
1987-2012) in copyright notices on source files.  As described at 
:

* This requires a notice in README about the use of range notation; I 
propose such a notice below.

* It is not necessary to track the modification dates of individual files, 
only the package as a whole; as there have been public GCC releases or 
public version control in each year from 1987 onwards, the form 
-2012 is OK for all GCC source files (whose source is in GCC 
rather than being copied from another package) as long as  is 
1987 or later.

Comments?  GDB and glibc already make active use of ranges (as does the 
Ada front end in GCC).  I think it's a useful cleanup to convert source 
files to the -2012 form, and to set up automatic updates of 
all files at the start of the year so people don't need to care about 
copyright notice updates for the rest of the year, but don't plan to work 
on these things myself.  (gnulib has a script that can help with both of 
those things.  glibc has been converting individual files to the single 
range form whenever the dates needed updating to include 2012, but may do 
a general bulk conversion later.)

2012-06-30  Joseph Myers  

* README: Document use of ranges of years in copyright notices.

Index: README
===
--- README  (revision 189094)
+++ README  (working copy)
@@ -15,3 +15,8 @@
 version of the manual is in the files gcc/doc/gcc.info*.
 
 See http://gcc.gnu.org/bugs/ for how to report bugs usefully.
+
+Copyright years on GCC source files may be listed using range
+notation, e.g., 1987-2012, indicating that every year in the range,
+inclusive, is a copyrightable year that could otherwise be listed
+individually.

-- 
Joseph S. Myers
jos...@codesourcery.com

Re: Allow use of ranges in copyright notices

[David Edelsohn]

On Sat, Jun 30, 2012 at 10:58 AM, Joseph S. Myers
 wrote:
> I propose that GCC should allow the use of ranges of years (e.g.
> 1987-2012) in copyright notices on source files.  As described at
> :
>
> * This requires a notice in README about the use of range notation; I
> propose such a notice below.
>
> * It is not necessary to track the modification dates of individual files,
> only the package as a whole; as there have been public GCC releases or
> public version control in each year from 1987 onwards, the form
> -2012 is OK for all GCC source files (whose source is in GCC
> rather than being copied from another package) as long as  is
> 1987 or later.
>
> Comments?  GDB and glibc already make active use of ranges (as does the
> Ada front end in GCC).  I think it's a useful cleanup to convert source
> files to the -2012 form, and to set up automatic updates of
> all files at the start of the year so people don't need to care about
> copyright notice updates for the rest of the year, but don't plan to work
> on these things myself.  (gnulib has a script that can help with both of
> those things.  glibc has been converting individual files to the single
> range form whenever the dates needed updating to include 2012, but may do
> a general bulk conversion later.)

IBM's policy specifies a comma:

, 

and not a dash range.

- David

gcc-4.7-20120630 is now available

[gccadmin]

Snapshot gcc-4.7-20120630 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20120630/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 4.7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_7-branch 
revision 189095

You'll find:

 gcc-4.7-20120630.tar.bz2 Complete GCC

  MD5=05394fb34461e1f79e73cc81739ab69f
  SHA1=cc201cf332ee1f95627d5b415ae4d7b4310f1322

Diffs from 4.7-20120623 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.7
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.