unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: spiegel@genion.de
Cc: spiegel@gnu.org, emacs-devel@gnu.org
Subject: Re: deleting rcs keywords from emacs sources
Date: Tue, 23 Mar 2004 18:46:09 +0000 (GMT)	[thread overview]
Message-ID: <4242667.1080067569994.JavaMail.root@tintin.london.ongenie.net> (raw)

As it looks like I'm the only one who sees any benefit in version headers, 
I certainly won't insist on keeping them in there.

> if they're actively tracking CVS, they can easily
> enough get the cvs revision with `cvs status').

Is that really the only answer?  To find out what version of a file you are 
looking at, you need to be hooked up to the version control system?  I often 
send files back and forth, and frequently I need to decide what version 
I'm looking at, with the file being isolated from its version control history.

I find it completely natural, even essential that a file is stamped with the 
version it contains, the stamp being a part of the actual contents of the 
file.

It should be the job of the version control system to ignore this kind of 
changes for operations where it clearly doesn't make sense.  CVS, as somebody 
pointed out, is capable of this for the headers it produces.

I have occasionally received bug reports about old versions of vc.el which didn't 
have any headers in them.  People were astonished that the version control 
part of emacs didn't contain this essential versioning information itself.

             reply	other threads:[~2004-03-23 18:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 18:46 spiegel [this message]
2004-03-23 21:47 ` deleting rcs keywords from emacs sources 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
  -- strict thread matches above, loose matches on Subject: below --
2004-03-23  6:46 Miles Bader
2004-03-23  7:47 ` Eli Zaretskii
2004-03-23 10:56   ` Kim F. Storm
2004-03-23  9:51 ` spiegel
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-24  5:34             ` Richard Stallman
2004-03-23 15:04         ` Stefan Monnier
2004-03-23 18:17       ` Nick Roberts
2004-03-23 18:07     ` Nick Roberts
2004-03-24  5:34 ` Richard Stallman
2004-03-25  8:17   ` Miles Bader

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=4242667.1080067569994.JavaMail.root@tintin.london.ongenie.net \
    --to=spiegel@genion.de \
    --cc=emacs-devel@gnu.org \
    --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).