From: Mike Stump <mikestump@comcast.net>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Andrew Pinski <pinskia@gmail.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [committed] 2011 and 2012 Copyright year updates
Date: Sun, 06 Jan 2013 20:24:00 -0000 [thread overview]
Message-ID: <5062A1B1-87A9-4C06-865D-E3FF0F6FA861@comcast.net> (raw)
In-Reply-To: <87ip7a5x1v.fsf@talisman.default>
On Jan 6, 2013, at 4:13 AM, Richard Sandiford <rdsandiford@googlemail.com> wrote:
> Anyway, here's my attempt a script to convert to ranges and, if enabled,
> to include the current year.
I don't think we should update to 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.
I've audited the change… I noticed an inconsistent use of:
Copyright (c) 2010
Copyright 1992
Copyright (C) 2010
but that is pre-existing. Also, I noticed a 90-2007, which should canonicalized to 1990-2007, but that is also pre-existing.
I did the analysis by case reduction so that like case classes reduce to generalized forms and then I audited all the forms of changes that appeared. This lets me skip quickly the majority of changes and focus in on just the weirdest of the weird quickly and accurately without missing them in the noise of the common cases.
Look good. I think we should put it in. I didn't audit upstream or out of tree files. Only the form of the change.
next prev parent reply other threads:[~2013-01-06 20:24 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
2013-01-06 21:48 ` Richard Sandiford
2013-01-07 8:56 ` Richard Biener
2013-01-06 20:24 ` Mike Stump [this message]
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=5062A1B1-87A9-4C06-865D-E3FF0F6FA861@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=pinskia@gmail.com \
--cc=rdsandiford@googlemail.com \
/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).