unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andre Spiegel <spiegel@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: deleting rcs keywords from emacs sources
Date: Thu, 25 Mar 2004 08:45:08 +0100	[thread overview]
Message-ID: <1080200708.749.486.camel@localhost> (raw)
In-Reply-To: <20040323214737.GA21737@fencepost>

On Tue, 2004-03-23 at 22:47, Miles Bader wrote:

> > 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.
> 
> Er, if you're making changes outside of CVS than the keyword info isn't
> going to be very useful, is it?

This has nothing to do with changes outside CVS.  The scenario usually
goes like this: Somebody reports a bug, I fix it.  The user doesn't have
CVS access, my fix is not readily backported into the version of the
file he has, so I send him the entire current source file.  Later, that
person has another problem, and reports it along with the version number
of the file I sent him.  Without version numbers in the files, this is 
very difficult, if not impossible to keep track of.

Now, *if* changes outside of CVS happen, then the version numbers in the
file at least give you a clear indication what CVS version this file was
based on, and then it's trivial to find out what these changes were,
relative to the corresponding CVS version.  This is very difficult to
find out if you have no idea what CVS version the file was based on.

I could go on and on with scenarios that are not Emacs-related, but
where version numbers also play an important role.  For example, people
sometimes print files on paper to carry into a review meeting.  Files
get deployed to machines with no access to the version control system
etc. etc.

> > 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.
> 
> I've seen others say this too, and I suspect that's a major reason people use
> rcs keywords -- it gives them warm fuzzies.

I think the scenarios above show the contrary.

> These keywords are the sort of thing that may seem like a great idea at
> first, but which come back to haunt you later (as we now see :-)

I used to think that the keywords, being a huge benefit for myself, did
not cause any trouble elsewhere.  But if they really do, then the cost
vs. the benefit needs to be weighed of course.  As it appears that
several people are suffering trouble, I won't insist on my objections.

In the general case (i.e. outside Emacs development), I firmly believe
that this needs to be handled properly, because surely, many projects
and shops will insist on having such a feature.  If it takes effort to
reconcile this with merging etc., so be it.  A feature is not bad just
because it is non-trivial to implement.

  reply	other threads:[~2004-03-25  7:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 18:46 deleting rcs keywords from emacs sources spiegel
2004-03-23 21:47 ` Miles Bader
2004-03-25  7:45   ` Andre Spiegel [this message]
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=1080200708.749.486.camel@localhost \
    --to=spiegel@gnu.org \
    --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).