* Re: MH-E commits
[not found] <E18fnfs-0004Md-01@monty-python.gnu.org>
@ 2003-02-04 7:39 ` Eli Zaretskii
2003-02-04 23:51 ` Bill Wohler
2003-02-05 0:14 ` Richard Stallman
0 siblings, 2 replies; 3+ messages in thread
From: Eli Zaretskii @ 2003-02-04 7:39 UTC (permalink / raw)
Cc: Bill Wohler
> Index: emacs/lisp/mh-e/mh-utils.el
> diff -c emacs/lisp/mh-e/mh-utils.el:1.1 emacs/lisp/mh-e/mh-utils.el:1.2
> *** emacs/lisp/mh-e/mh-utils.el:1.1 Sat Jan 25 21:38:37 2003
> --- emacs/lisp/mh-e/mh-utils.el Mon Feb 3 15:55:30 2003
> ***************
> *** 30,36 ****
>
> ;;; Change Log:
>
> ! ;; $Id: mh-utils.el,v 1.1 2003/01/26 02:38:37 wohler Exp $
>
> ;;; Code:
>
> --- 30,36 ----
>
> ;;; Change Log:
>
> ! ;; $Id: mh-utils.el,v 1.2 2003/02/03 20:55:30 wohler Exp $
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)?
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: MH-E commits
2003-02-04 7:39 ` MH-E commits Eli Zaretskii
@ 2003-02-04 23:51 ` Bill Wohler
2003-02-05 0:14 ` Richard Stallman
1 sibling, 0 replies; 3+ messages in thread
From: Bill Wohler @ 2003-02-04 23:51 UTC (permalink / raw)
Cc: emacs-devel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MH-E commits
2003-02-04 7:39 ` MH-E commits Eli Zaretskii
2003-02-04 23:51 ` Bill Wohler
@ 2003-02-05 0:14 ` Richard Stallman
1 sibling, 0 replies; 3+ messages in thread
From: Richard Stallman @ 2003-02-05 0:14 UTC (permalink / raw)
Cc: emacs-devel
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 try to discourage them, but have not been rigidly strict about it.
They cause hassle when people edit the files in their own repositories
and then send changes to us. In the case of MH-E, if the editing is
only done in our repository now, maybe they don't do any harm.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-02-05 0:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2003-02-05 0:14 ` Richard Stallman
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).