From: David Kastrup <dak@gnu.org>
To: David Reitter <david.reitter@gmail.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>, Eli Zaretskii <eliz@gnu.org>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Bazaar references complicate the git transition
Date: Sat, 11 Jan 2014 21:36:17 +0100 [thread overview]
Message-ID: <877ga6fe7y.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <F7962D51-2B3E-4DAE-A19F-95C036037816@gmail.com> (David Reitter's message of "Sat, 11 Jan 2014 15:13:32 -0500")
David Reitter <david.reitter@gmail.com> writes:
> Eric,
>
> Here's an idea - why don't you just tag each referenced revision in
> git with the bzr revision id, e.g.,
>
> git tag 'bzr/115967' de7d9800
>
> That would make it trivial and seamless to find a reference later on.
> I would update the change log files to use the same bzr/ prefix.
>
> You can do this after the transition is done, and if people don't like
> it, they can undo it in the future.
Aaaaaaand we have a winner.
The only downside is that a list of all current tags will be, uhm,
unpretty. But it is so already. And when tagging only every
_referenced_ version, this should not be too bad.
--
David Kastrup
next prev parent reply other threads:[~2014-01-11 20:36 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 [this message]
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
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=877ga6fe7y.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--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).