all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Karl Fogel <kfogel@red-bean.com>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Repo cpnversion progress report
Date: Fri, 31 Jan 2014 16:03:00 -0500	[thread overview]
Message-ID: <jwvwqhfvpfn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20140131181612.GA18170@thyrsus.com> (Eric S. Raymond's message of "Fri, 31 Jan 2014 13:16:12 -0500")

> I hear the argument about forensics, but the Bazaar revision numbers
> are no more helpful for that than the action stamps. If anything,
> spelunking is an argument for appending those numbers to the change
> comment of each revision - leaving them in as references would a
> bass-ackwards approach to the problem.

Moving the "equiv to bzr r123456" to the commit message of that
corresponding Git commit sounds like an good compromise.  Of course, we
don't need it for every commit, but for all those commits that have
a corresponding "action stamp".

> But there's a better way.  We're going to have a complete
> revision-to-action-stamp map as part of the record.  It would be
> pretty easy to write Emacs code that uses that map to find revisions
> by Bazaar reference number.  That's the right solution, IMO.

But where would this map be stored?
Keeping it directly in the commit log sounds like a better approach.


        Stefan



  parent reply	other threads:[~2014-01-31 21:03 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=jwvwqhfvpfn.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=kfogel@red-bean.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 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.