From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: one more question about year ranges in copyright notices...
Date: Wed, 04 Jan 2012 16:43:00 -0000 [thread overview]
Message-ID: <m37h17bepx.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F047C06.8030000@earthlink.net> (Stan Shebs's message of "Wed, 04 Jan 2012 08:19:18 -0800")
>>>>> "Stan" == Stan Shebs <stanshebs@earthlink.net> writes:
Stan> For files with new code, it would be nice if the first year in the
Stan> pair could be the year of the file's creation - it's a little jarring
Stan> to see something like tic6x-tdep.c with a 1986 date at the top of it.
FWIW, I usually use the original dates if I copy-and-paste a file.
I'm not sure if this is really what we're supposed to do, though.
Tom
next prev parent reply other threads:[~2012-01-04 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:47 Joel Brobecker
2012-01-04 16:10 ` Tom Tromey
2012-01-04 16:19 ` Stan Shebs
2012-01-04 16:43 ` Tom Tromey [this message]
2012-01-04 16:55 ` Pedro Alves
2012-01-04 17:17 ` Joseph S. Myers
2012-01-04 17:38 ` Alfred M. Szmidt
2012-01-04 17:28 ` Alfred M. Szmidt
2012-01-06 6:23 ` Joel Brobecker
2012-01-27 9:23 ` Joel Brobecker
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=m37h17bepx.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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