From: Andrew Pinski <pinskia@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed] 2011 and 2012 Copyright year updates
Date: Fri, 04 Jan 2013 16:44:00 -0000 [thread overview]
Message-ID: <CA+=Sn1kJqBh_rUFtPvvJe+AVXUAT8EiAYQ_0e-oWp8QKofSphw@mail.gmail.com> (raw)
In-Reply-To: <20130104125437.GN7269@tucnak.redhat.com>
On Fri, Jan 4, 2013 at 4:54 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> Hi!
>
> I've run a script to notice gcc maintained files with FSF copyright that
> have been modified in 2011 and/or 2012 (according to svn log, ignoring
> r168438 and r184997 commits), but didn't have years 2011 and/or 2012
> included in Copyright lines. I've kept the preexisting style, so
> where year ranges were used, updated those if needed, if not, kept the
> year lists.
Can't we just move to ranges of years now that the FSF approves of
them. They even approve of ranges where a file was not touched during
that year. This seems better than listing all the years out.
Thanks,
Andrew
next prev parent reply other threads:[~2013-01-04 16: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 [this message]
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
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='CA+=Sn1kJqBh_rUFtPvvJe+AVXUAT8EiAYQ_0e-oWp8QKofSphw@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).