From: Richard Stallman <rms@gnu.org>
Cc: miles@gnu.org, snogglethorpe@gmail.com, darkman_spam@yahoo.fr,
emacs-devel@gnu.org
Subject: Re: Ignoring file local-variables in patches?
Date: Wed, 05 Jan 2005 15:08:04 -0500 [thread overview]
Message-ID: <E1CmHRs-0004hr-FU@fencepost.gnu.org> (raw)
In-Reply-To: <ilufz1gd436.fsf@latte.josefsson.org> (message from Simon Josefsson on Wed, 05 Jan 2005 03:03:57 +0100)
Proposed solution: Have copyright-update search the next 10 lines
after the first found copyright line, to see if it can find more
current copyright headers to update.
It sounds like a good idea to me.
prev parent reply other threads:[~2005-01-05 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 23:20 Ignoring file local-variables in patches? drkm
2005-01-05 0:12 ` Miles Bader
2005-01-05 2:03 ` Simon Josefsson
2005-01-05 2:30 ` Miles Bader
2005-01-05 4:34 ` Stefan Monnier
2005-01-05 20:08 ` Richard Stallman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1CmHRs-0004hr-FU@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=darkman_spam@yahoo.fr \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=snogglethorpe@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).