From: spiegel@genion.de
Cc: spiegel@gnu.org
Subject: Re: deleting rcs keywords from emacs sources
Date: Tue, 23 Mar 2004 09:51:11 +0000 (GMT) [thread overview]
Message-ID: <5192113.1080035471618.JavaMail.root@tintin.london.ongenie.net> (raw)
> [...] and as far as I know aren't really particularly useful,
> so I'd like to simply delete them from the
> emacs sources.
I absolutely, positively couldn't live without them. I have in fact doubts whether
intelligent life on earth would be possible at all without them. Of course
that could be just me, so I'm open for counter-arguments :-)
I have used these keywords on countless occasions in VC maintenance. I don't
know how I should identify the file versions that people are talking about
without these stamps inside the files. It is true that as long as people
use vanilla code from an Emacs release, they can always say "I have this
problem with VC from Emacs 21.x", but it is still easier for me if they
just say "vc.el version 1.311 barfs on me". Then I don't have to go looking
which version we shipped with Emacs 21.x (if a release tag was applied at
all).
Identifying the version becomes impossible when I send people an updated copy
of vc.el (which I often do), or they grab it from CVS.
What other means would be available? Should I ask for an md5sum of the
file, or a copy of the file itself and diff it against my copy?
If the headers are a problem during merging, I think it would be very worthwhile
to implement a way for the merge operation to ignore them. That would be
helpful for many people like myself for whom the version headers are an
integral part of their work routine. (Incidentally, a user once reported
a VC bug to me in an old version that didn't have headers in the file, and
he was astonished that he couldn't find any.)
As I said, I am certainly open for alternatives (incidentally, does your remark
mean that arch doesn't have version headers at all, Miles)?
Sorry for the rough writeup and the unfamiliar e-mail address, I'm writing from
a customer site.
Andre
next prev reply other threads:[~2004-03-23 9:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 6:46 deleting rcs keywords from emacs sources Miles Bader
2004-03-23 7:47 ` Eli Zaretskii
2004-03-23 10:56 ` Kim F. Storm
2004-03-23 9:51 ` spiegel [this message]
2004-03-23 10:16 ` Miles Bader
2004-03-23 11:41 ` Juanma Barranquero
2004-03-23 13:13 ` Miles Bader
2004-03-23 14:01 ` Juanma Barranquero
2004-03-23 14:35 ` Miles Bader
2004-03-23 14:58 ` Juanma Barranquero
2004-03-23 15:14 ` Stefan Monnier
2004-03-23 15:36 ` Juanma Barranquero
2004-03-23 23:38 ` deleting rcs " David Kastrup
2004-03-24 5:34 ` deleting rcs keywords " Richard Stallman
2004-03-23 15:04 ` Stefan Monnier
2004-03-23 15:39 ` Wheter to switch to another VC, and which one Juanma Barranquero
2004-03-23 16:25 ` Stefan Monnier
2004-03-23 16:43 ` Masatake YAMATO
2004-03-23 17:17 ` Stefan Monnier
2004-03-23 17:31 ` Masatake YAMATO
2004-03-23 18:50 ` Stefan Monnier
2004-03-24 0:17 ` Kim F. Storm
2004-03-23 23:35 ` Miles Bader
2004-03-24 10:52 ` Kim F. Storm
2004-03-24 10:24 ` Miles Bader
2004-03-24 17:48 ` Stefan Monnier
2004-03-23 18:17 ` deleting rcs keywords from emacs sources Nick Roberts
2004-03-23 18:07 ` Nick Roberts
2004-03-24 5:34 ` Richard Stallman
2004-03-25 8:17 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 18:46 spiegel
2004-03-23 21:47 ` Miles Bader
2004-03-25 7:45 ` Andre Spiegel
2004-03-26 16:45 ` Richard Stallman
2004-03-26 18:10 ` Stefan Monnier
2004-03-26 18:46 ` David Kastrup
2004-03-28 1:36 ` Richard Stallman
2004-03-26 19:05 ` Robert J. Chassell
2004-03-26 19:37 ` Andre Spiegel
2004-03-28 1:36 ` Richard Stallman
2004-03-28 11:10 ` Andre Spiegel
2004-03-29 20:56 ` Richard Stallman
2004-03-30 14:22 ` Andre Spiegel
2004-03-31 15:05 ` 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=5192113.1080035471618.JavaMail.root@tintin.london.ongenie.net \
--to=spiegel@genion.de \
--cc=spiegel@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).