From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Copyright notices
Date: Sat, 11 Feb 2006 14:36:00 -0000 [thread overview]
Message-ID: <20060211143620.GA20537@nevyn.them.org> (raw)
In-Reply-To: <uhd76xif1.fsf@gnu.org>
On Sat, Feb 11, 2006 at 01:07:46PM +0200, Eli Zaretskii wrote:
> Since it took me by surprise, I thought that maybe other maintainers
> aren't aware of this text from maintain.texi, which says how to update
> copyright years in the files' copyright notices:
If you think this was surprising, you should see the first version that
was posted to gnu-prog; it read as if doing so was required rather than
optional. I understand the FSF's reasoning here (even if it seems
somewhat strange to me).
> Perhaps we should have a script to do the same once a year, and stop
> worrying about updating the individual notices when we modify each
> file.
I think this is not a bad idea. The current set of notices are fairly
accurate - I won't say 100%, but maybe 95% - so I think that being
able to add a year by script would meet our needs.
Emacs already has some widgetry to add copyright years, doesn't it?
Can that easily work on a list of files?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-11 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 11:08 Eli Zaretskii
2006-02-11 11:13 ` Robert Dewar
2006-02-11 16:33 ` Eli Zaretskii
2006-02-12 3:15 ` Robert Dewar
2006-02-11 14:36 ` Daniel Jacobowitz [this message]
2006-02-11 16:30 ` Eli Zaretskii
2006-02-11 18:27 ` Daniel Jacobowitz
2006-02-11 19:05 ` Eli Zaretskii
2006-02-11 19:07 ` Daniel Jacobowitz
2006-02-11 19:18 ` Eli Zaretskii
2006-02-11 20:31 ` Daniel Jacobowitz
2006-02-11 19:19 ` Bob Rossi
2006-02-11 21:55 ` Eli Zaretskii
2006-02-12 6:09 ` Jim Blandy
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=20060211143620.GA20537@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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