From: Alex Bennee <kernel-hacker@bennee.com>
To: git@vger.kernel.org
Subject: What is the current best bi-directional git<->bzr method?
Date: Tue, 19 May 2009 15:08:22 +0100 [thread overview]
Message-ID: <b2cdc9f30905190708t1e170106oce3c577933c99247@mail.gmail.com> (raw)
Hi,
I'm starting to mess around with project on Launchpad which are all
hosted with bzr. Short of convincing these projects to switch DVCS
just for me I need a decent bi-directional way of dealing with bzr
archives.
I found a script[1] which I have hacked a bit[2] to import repo's
fine. However going the other way doesn't seem to work. Before I mess
around too much further I though I'd check if there are any known
working gateways at the moment?
[1] http://github.com/pieter/git-bzr/tree/master
[2] http://github.com/stsquad/git-bzr/tree/master
--
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php
next reply other threads:[~2009-05-19 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 14:08 Alex Bennee [this message]
2009-05-19 15:51 ` What is the current best bi-directional git<->bzr method? Pieter de Bie
2009-05-19 20:31 ` Alex Bennee
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=b2cdc9f30905190708t1e170106oce3c577933c99247@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).