From: Jakub Jelinek <jakub@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>,
gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com,
Richard Biener <rguenther@suse.de>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: [committed] 2011 and 2012 Copyright year updates
Date: Sun, 06 Jan 2013 12:44:00 -0000 [thread overview]
Message-ID: <20130106124405.GW7269@tucnak.redhat.com> (raw)
In-Reply-To: <87ip7a5x1v.fsf@talisman.default>
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
next prev parent reply other threads:[~2013-01-06 12:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 12:54 Jakub Jelinek
2013-01-04 16:44 ` Andrew Pinski
2013-01-04 16:49 ` Jakub Jelinek
2013-01-06 12:14 ` Richard Sandiford
2013-01-06 12:44 ` Jakub Jelinek [this message]
2013-01-06 21:48 ` Richard Sandiford
2013-01-07 8:56 ` Richard Biener
2013-01-06 20:24 ` Mike Stump
2013-01-06 20:37 ` Mike Stump
2013-01-06 21:53 ` Richard Sandiford
2013-01-07 16:00 ` Joseph S. Myers
2013-01-07 19:49 ` Richard Sandiford
2013-01-07 19:59 ` Bruce Korb
2013-01-07 20:22 ` Richard Sandiford
2013-01-07 20:30 ` Bruce Korb
2013-01-07 20:31 ` Joseph S. Myers
2013-01-08 20:49 ` Richard Sandiford
2013-01-10 14:17 ` Jakub Jelinek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130106124405.GW7269@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=pinskia@gmail.com \
--cc=rdsandiford@googlemail.com \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).