On Sun, Jan 06, 2013 at 12:13:32PM +0000, Richard Sandiford wrote:
> I never remember to update the copyright years, so I thought I'd have a go.
> And you were right of course. It ended up being a huge time sink.
>
> Anyway, here's my attempt a script to convert to ranges and, if enabled,
> to include the current year. The script only updates FSF copyright notices
> and leaves others alone. I've tried my best to make sure that licences
> and imported FSF sources aren't touched, but I could have missed some cases.
Looks reasonable to me, though I'd like to hear richi's and Joseph's
opinion too.
I've noticed a minor nit:
--- gcc.orig/gcc/testsuite/gcc.misc-tests/linkage.exp
+++ gcc/gcc/testsuite/gcc.misc-tests/linkage.exp
@@ -1,5 +1,4 @@
-# Copyright (C) 1988, 90-96, 1997, 2000, 2001, 2002, 2007, 2008, 2010,
-# 2011,
-# 2012 Free Software Foundation, Inc.
+# Copyright (C) 90-2012 Free Software Foundation, Inc.
That should have been presumably 1988-2012, haven't looked at other similar
cases. As for updating to -2013, I think it isn't appropriate for all
files, e.g. I'd leave ChangeLog* and various README* files to keep their
finish date as is, say ChangeLog.2003 can be just Copyright (c) 2003,
doesn't need to be 2003-2013. Perhaps just automatically add -2013 to gcc
(except gcc/testsuite) *.[ch], *.md, *.def, *.opt files or so, plus
gcc/testsuite *.exp files? E.g. testsuite *.c/*.C files that are Copyright
2004 don't need to be -2013?
Also, just a remainder, any Copyright line change in libstdc++-v3/include
might potentially require adjustments to libstdc++-v3/testsuite/, because
various tests have header line numbers hardcoded in them.
Jakub
