unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joshua Judson Rosen <rozzin@geekspace.com>
To: esr@thyrsus.com
Cc: David Reitter <david.reitter@gmail.com>,
	Eli Zaretskii <eliz@gnu.org>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Converting bzr revision-IDs to action stamps (was: Bazaar references complicate the git transition)
Date: Sun, 12 Jan 2014 00:39:56 -0500	[thread overview]
Message-ID: <87y52l3gib.fsf@slice.rozzin.com> (raw)
In-Reply-To: <20140111234506.GB18174@thyrsus.com> (Eric S. Raymond's message of "Sat, 11 Jan 2014 18:45:06 -0500")

"Eric S. Raymond" <esr@thyrsus.com> writes:
>
> Joshua Judson Rosen <rozzin@geekspace.com>:
> >
> > It may or may not be true specifically in the case of the mainline emacs
> > revision history; someone will probably need/want to check (if nobody
> > has yet), because it's certainly _possible_ to have situations in bzr
> > where `timestamp!committer' works as a sort of hash bucket but _isn't_
> > specific enough to identify a single unique revision-object.
>
> I know. That's why the *full* form of an action stamp is actually
>
>   {ISO-date }!{email-address}#{sequence-nummber}

Ah, OK--I see that in the reposurgeon manual, now.

I was looking for something like that in your "RFC: Action stamps" post
<http://esr.ibiblio.org/?p=3872> and couldn't find it there.

Is the reposurgeon manual the authoritative document on action stamps?
Or is there another doc with more information? (`more information'
being, e.g., the points in various comments attached to
<http://esr.ibiblio.org/?p=4854>)

(all of this is only really relevant to the matter at hand _if_ there
 are collisions, of course)

> I have needed that generality on some Subversion repositories.

Hunh. It's much less obvious to me why that would happen in svn.

-- 
"'tis an ill wind that blows no minds."



  reply	other threads:[~2014-01-12  5:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 15:54 Bazaar references complicate the git transition Eric S. Raymond
2014-01-11 16:15 ` Juanma Barranquero
2014-01-11 16:29   ` Eric S. Raymond
2014-01-11 16:53     ` Juanma Barranquero
2014-01-11 16:24 ` David Kastrup
2014-01-11 16:40   ` Eric S. Raymond
2014-01-11 17:23     ` Juanma Barranquero
2014-01-11 22:47     ` Timur Aydin
2014-01-11 23:40       ` Eric S. Raymond
2014-01-11 16:36 ` Eli Zaretskii
2014-01-11 16:43   ` Eric S. Raymond
2014-01-11 17:10 ` David Reitter
2014-01-11 17:27   ` Eric S. Raymond
2014-01-11 17:46     ` David Kastrup
2014-01-11 18:00       ` Andreas Schwab
2014-01-11 18:04     ` Eli Zaretskii
2014-01-11 18:08       ` Eli Zaretskii
2014-01-11 18:24         ` Óscar Fuentes
2014-01-11 19:15           ` Thien-Thi Nguyen
2014-01-11 19:46             ` Eli Zaretskii
2014-01-11 19:36           ` Paul Eggert
2014-01-11 20:53             ` Eric S. Raymond
2014-01-11 20:13         ` David Reitter
2014-01-11 20:36           ` David Kastrup
2014-01-11 21:26           ` Eric S. Raymond
2014-01-11 22:22             ` David Reitter
2014-01-11 23:03             ` Converting bzr revision-IDs to action stamps (was: Bazaar references complicate the git transition) Joshua Judson Rosen
2014-01-11 23:45               ` Eric S. Raymond
2014-01-12  5:39                 ` Joshua Judson Rosen [this message]
2014-01-12 12:43                   ` Eric S. Raymond
2014-01-11 18:39 ` Bazaar references complicate the git transition Richard Stallman
2014-01-12  3:14   ` Stefan Monnier
2014-01-12  3:55     ` Eric S. Raymond
2014-01-12 22:25       ` Stefan Monnier
2014-01-12 23:02         ` Eric S. Raymond
2014-01-13  2:28         ` Glenn Morris
2014-01-13  3:42           ` Stefan Monnier
2014-01-12 13:44     ` Richard Stallman

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=87y52l3gib.fsf@slice.rozzin.com \
    --to=rozzin@geekspace.com \
    --cc=david.reitter@gmail.com \
    --cc=eliz@gnu.org \
    --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).