all messages for Emacs-related lists mirrored at yhetil.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: Tue, 30 Mar 2004 16:22:44 +0200	[thread overview]
Message-ID: <1080656564.29733.69.camel@localhost> (raw)
In-Reply-To: <E1B83nv-00055h-SH@fencepost.gnu.org>

On Mon, 2004-03-29 at 22:56, Richard Stallman wrote:

>     The problem with this approach is that the files would only be stamped
>     when *I* send them out.  When somebody gets a file through a different
>     channel, e.g. via Web-CVS, or because somebody else sends it to him, the
>     file won't have an identification in it.
> 
> Is it a frequent occurrence for you that people report problems in
> versions that of VC they got from CVS in this way, without updating
> Emacs as a whole from CVS?  Very few of the bug reports that I see
> seem to describe such cases.

It is hard to tell how frequent this is, because in the past, the files
people were referring to always contained version numbers, and so I
wouldn't know which path they actually took.

Myself, I have just recently built and installed a CVS snapshot of Emacs
at a customer site, because we needed some of the new features that are
not in any actual release yet.  I would assume that such installations
occur frequently all over the world, especially since there is so much
time between Emacs releases.  The installed source files are indeed
disconnected from their CVS history.  Now, if anybody were to discover a
bug in such an installation, in a source file without version headers in
it, it would be difficult to track down.

I don't have hard numbers for this.  I'm referring to potential
problems, which might turn out more or less severe.  (If I'm anywhere
near correct, it ought to be happening already for other files, which I
don't maintain, and which never had version headers in them.  Only other
developers could testify to that.)

You say that "very few" of the bug reports you see seem to describe such
cases.  So, if it actually does occur, and version headers would help
with these cases, then that appears to be an argument to keep them, and
to solve the problems they cause by some other means.

  reply	other threads:[~2004-03-30 14:22 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1080656564.29733.69.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.