unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: esr@thyrsus.com
Cc: emacs-devel@gnu.org
Subject: Re: Repo cpnversion progress report
Date: Fri, 31 Jan 2014 11:44:23 -0800	[thread overview]
Message-ID: <52EBFD17.1050006@cs.ucla.edu> (raw)
In-Reply-To: <20140131181612.GA18170@thyrsus.com>

Eric S. Raymond wrote:
> I hear the argument about forensics, but the Bazaar revision numbers
> are no more helpful for that than the action stamps.

As someone who regularly spelunks back decades, I'd prefer keeping these 
stamps as small as possible.  Even 
"2003-07-05T12:41:24!Roland.Winkler@physik.uni-erlangen.de" will cause 
hassles, and I especially wouldn't want to read and digest monsters 
along the lines of what someone else proposed, e.g., 
"1985-04-18T00:49:29!jimb@redhat.com (bzr 1) (CVS 4.35.2.1) (RCS 1.71) 
(emacs-backup ~107~)".  It doesn't scale for a revision string to 
contain all the names that the revision has ever had, for all the 
version-control systems we've ever used.

It may be that leaving commentary alone is the simplest and best way to 
keep it short and readable, with a map elsewhere that converts old 
notation.  That being said, I'm willing to give your approach a try.  As 
long as the complete history is available somewhere and is documented, 
and it's not too much work to use it, it should be OK.

PS.  In that 1985 example, the email address jimb@redhat.com is 
ahistorical, as Red Hat didn't exist in 1985.  That info is taken 
straight from the current bzr repository.  Most likely the repository 
was made ahistorical during an earlier conversion, unfortunately.



  reply	other threads:[~2014-01-31 19:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 19:55 Repo cpnversion progress report Eric S. Raymond
2014-01-30 20:11 ` Andreas Schwab
2014-01-30 20:27   ` Eric S. Raymond
2014-01-30 22:04     ` Andreas Schwab
2014-01-30 21:23 ` Eli Zaretskii
2014-01-30 21:42   ` Eric S. Raymond
2014-01-31  7:50     ` Eli Zaretskii
2014-01-31 15:25       ` Eric S. Raymond
2014-01-31 15:57         ` David Kastrup
2014-01-31 16:15         ` Eli Zaretskii
2014-01-31 17:31       ` Karl Fogel
2014-01-31 17:56         ` Juanma Barranquero
2014-01-31 19:23           ` Eric S. Raymond
2014-01-31 19:55             ` Juanma Barranquero
2014-01-31 20:30             ` Eli Zaretskii
2014-01-31 21:20             ` Sean Sieger
2014-01-31 21:22             ` Sean Sieger
2014-02-01  9:38             ` David Kastrup
2014-01-31 19:31           ` Karl Fogel
2014-01-31 20:18             ` Eli Zaretskii
2014-02-01 11:04             ` Richard Stallman
2014-01-31 18:16         ` Eric S. Raymond
2014-01-31 19:44           ` Paul Eggert [this message]
2014-01-31 21:07             ` Eric S. Raymond
2014-02-01  0:05               ` Paul Eggert
2014-02-01  0:25                 ` Juanma Barranquero
2014-02-01  4:19                 ` Eric S. Raymond
2014-02-01  8:40                 ` Eli Zaretskii
2014-02-02  1:03                 ` Stefan Monnier
2014-01-31 21:03           ` Stefan Monnier
2014-01-31 21:51             ` Eric S. Raymond
2014-01-31 23:15               ` Jan D.
2014-02-01  4:22                 ` Eric S. Raymond
2014-01-31 23:16               ` Stefan Monnier
2014-02-01  4:26                 ` Eric S. Raymond
2014-02-01 11:04                 ` Eli Zaretskii
2014-02-02  0:58                   ` Stefan Monnier
2014-02-02 10:24                     ` Eric S. Raymond

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=52EBFD17.1050006@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    /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).