From: Eli Zaretskii <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sourceware.org
Subject: Re: Copyright notices
Date: Sat, 11 Feb 2006 21:55:00 -0000 [thread overview]
Message-ID: <uzmkxwoev.fsf@gnu.org> (raw)
In-Reply-To: <20060211192051.GA4207@brasko.net> (message from Bob Rossi on Sat, 11 Feb 2006 14:20:51 -0500)
> Date: Sat, 11 Feb 2006 14:20:51 -0500
> From: Bob Rossi <bob@brasko.net>
>
> Of course, instead, you could use grep to look for files that 'find'
> produced and search for "Copyright (C)" to know what files should be
> updated. That way, you don't have to store a list of files that needs to
> be maintained.
The relevant Emacs command already does that--it searches for the
telltale Copyright strings and updates them, it doesn't just blindly
add a Copyright notice where none is present.
But that doesn't solve the problem that Daniel pointed out, since the
generated files also have the Copyright notice. See the various
configure scripts, for example. We don't want to update those, but
instead should regenerate them whenever their source files get updated
with another year's copyright.
next prev parent reply other threads:[~2006-02-11 21:55 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
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 [this message]
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=uzmkxwoev.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--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