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: Sun, 28 Mar 2004 13:10:26 +0200	[thread overview]
Message-ID: <1080472226.749.657.camel@localhost> (raw)
In-Reply-To: <E1B7PDg-0001uv-MJ@fencepost.gnu.org>

On Sun, 2004-03-28 at 03:36, Richard Stallman wrote:

> I asked that question so I can get an idea of how much
> inconvenience it would be for you.

The time I would need to put a timestamp into a file before I send it to
someone is surely negligible.  I assume between 5-10 seconds.  Less than
that if I write myself a clever macro for it.  I'd be doing it between
5-10 times a year, so that's your absolute measure of "inconvenience".

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.

As a result, I might get bug reports where we unknowingly talk about
different versions of a file.  It might take considerable time to sort
out such a misunderstanding.  This is a more severe kind of
"inconvenience" than the time I would need to make a timestamp manually.

Even if everything goes well, there would now be several different ways
to determine the version of a file: If it's from an Emacs release, use
the ChangeLog and CVS history.  If you're hooked up to CVS, use the CVS
version information.  If you get it via another channel, hope that
somebody put a timestamp into it.

To me, that seems messy and an inconvenience in itself.

  reply	other threads:[~2004-03-28 11:10 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 [this message]
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=1080472226.749.657.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).