From: Bill Wohler <wohler@newt.com>
Cc: emacs-devel@gnu.org
Subject: Re: MH-E commits
Date: Tue, 04 Feb 2003 15:51:59 -0800 [thread overview]
Message-ID: <200302042352.h14NpxRc026474@gbr.newt.com> (raw)
In-Reply-To: Pine.SUN.3.91.1030204093655.22830K-100000@is
Eli Zaretskii <eliz@is.elta.co.il> writes:
> I thought we considered the RCS/CVS keywords a pest because they tend to
> generate gratuitous changes like the one above. Is it possible to get
> rid of them (I thought we did that for all bundled packages)?
I was not aware of that convention. It certainly isn't in the Emacs
Lisp Coding Conventions. Where is this documented?
I include the RCS keyword because it adds a lot of useful information.
The gratuitous diffs are pesky indeed. However, it would be better to
fix the tools so that these diffs aren't generated.
Nonetheless, I notice that most (but not all) of the lisp packages do
not have the Id keyword, so I'll go with the flow and remove the
keywords from the MH-E package.
Is this important enough to take the time to punch out a patch release
now, or can it wait a month until our next regular release?
--
Bill Wohler <wohler@newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
next prev parent reply other threads:[~2003-02-04 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18fnfs-0004Md-01@monty-python.gnu.org>
2003-02-04 7:39 ` MH-E commits Eli Zaretskii
2003-02-04 23:51 ` Bill Wohler [this message]
2003-02-05 0:14 ` Richard Stallman
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=200302042352.h14NpxRc026474@gbr.newt.com \
--to=wohler@newt.com \
--cc=emacs-devel@gnu.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.
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).