From: Daniel Colascione <dancol@dancol.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Eli Zaretskii <eliz@gnu.org>,
bpt@hcoop.net, Fabian Ezequiel Gallina <galli.87@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Git to Bzr - what works?
Date: Wed, 15 Aug 2012 16:49:28 -0700 [thread overview]
Message-ID: <502C3588.1070707@dancol.org> (raw)
In-Reply-To: <jwvwr0z99bp.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
On 8/15/12 1:45 PM, Stefan Monnier wrote:
>> . When you have changes in the bzr repo:
>> . "bzr pull" from the git repo to the bzr branch created above
>
> But his Git repository is the result of a "Bzr->Git" conversion.
> So we'd get here a "Bzr->Git->Bzr" conversion. I strongly suspect that
> it is not an identity and that all the revids will be different.
I tried cloning a local git mirror (derived from the Savannah git
mirorr) using bzr-git. It's even slower than git-bzr. It's used 23
miutes of CPU time and processed 8315 of 122105 records.
>> . "bzr merge" to another bzr branch that tracks the Emacs trunk
>
> If indeed all the revids are different, this will either complain that
> there's no common ancestor (best case) or find some distant ancestor and
> pretty much double the size of the repository with a new copy of the
> whole history.
>
> This said, I don't understand the problem discussed here.
> Isn't "git-bzr" bidirectional (i.e. you can "git push" onto the Bzr
> repository)?
git-bzr would be great if it worked, but it doesn't work for me. After
chugging along for about an hour, it fails and complains about a
missing committer record.
How is the Savannah git mirror being generated? Matching its revids
would be the most important part of any bidirectional mirriroing
scheme. If Savannah is using git-bzr, I'd like to know the versions of
the pieces of software involved and whether the Savannah people made
any local modifications.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2012-08-15 23:49 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 1:35 Git to Bzr - what works? Daniel Colascione
2012-08-14 17:54 ` John Wiegley
2012-08-14 18:12 ` Eli Zaretskii
2012-08-14 19:56 ` BT Templeton
2012-08-15 2:49 ` Eli Zaretskii
2012-08-15 3:08 ` Fabian Ezequiel Gallina
2012-08-15 4:16 ` Stephen J. Turnbull
2012-08-15 17:56 ` Eli Zaretskii
2012-08-15 20:45 ` Stefan Monnier
2012-08-15 23:49 ` Daniel Colascione [this message]
2012-08-16 2:52 ` Eli Zaretskii
2012-08-16 3:19 ` John Wiegley
2012-08-16 15:25 ` Eli Zaretskii
2012-08-16 10:49 ` Julien Danjou
2012-08-16 12:09 ` Andreas Schwab
2012-08-17 2:27 ` Daniel Colascione
2012-08-17 7:06 ` Daniel Colascione
2012-08-21 16:59 ` Stefan Monnier
2012-08-15 17:22 ` John Wiegley
2012-08-15 17:43 ` Eli Zaretskii
2012-08-16 3:18 ` John Wiegley
2012-08-16 3:42 ` Óscar Fuentes
2012-08-16 15:27 ` Eli Zaretskii
2012-08-17 3:30 ` Stefan Monnier
2012-08-17 4:02 ` Daniel Colascione
2012-08-17 6:23 ` Eli Zaretskii
2012-08-17 7:12 ` Stephen J. Turnbull
2012-08-17 15:03 ` Richard Stallman
2012-08-16 15:23 ` Eli Zaretskii
2012-08-16 22:12 ` John Wiegley
2012-08-17 6:32 ` Eli Zaretskii
2012-12-21 15:05 ` Ted Zlatanov
2012-12-21 19:01 ` Karl Fogel
2012-12-22 5:44 ` Bastien
2012-12-22 12:24 ` Stephen J. Turnbull
2012-12-22 12:48 ` Stephen J. Turnbull
2012-12-22 13:21 ` Xue Fuqiao
2012-12-22 13:40 ` Juanma Barranquero
2012-12-22 13:51 ` Xue Fuqiao
2012-12-22 14:13 ` Andreas Schwab
2012-12-22 14:11 ` Andreas Schwab
2012-12-22 13:08 ` Bastien
2012-12-22 19:20 ` Ted Zlatanov
2012-12-21 23:42 ` Xue Fuqiao
2012-12-22 8:22 ` Juri Linkov
2012-12-22 17:04 ` Thomas Koch
2012-12-22 17:28 ` Thien-Thi Nguyen
2012-12-22 19:06 ` Ted Zlatanov
2012-12-24 5:56 ` Thien-Thi Nguyen
2012-12-24 13:31 ` Ted Zlatanov
2012-12-24 16:30 ` Thien-Thi Nguyen
2012-12-25 4:12 ` Bastien
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=502C3588.1070707@dancol.org \
--to=dancol@dancol.org \
--cc=bpt@hcoop.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=galli.87@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
/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.