From: Gabriel Filion <lelutin@gmail.com>
To: Miles Bader <miles@gnu.org>
Cc: git@vger.kernel.org, Chris Packham <judge.packham@gmail.com>,
conrad@metadecks.org
Subject: Re: RFD: git-bzr: anyone interested?
Date: Sat, 07 Aug 2010 04:48:02 -0400 [thread overview]
Message-ID: <4C5D1DC2.6000704@gmail.com> (raw)
In-Reply-To: <8762znjdr0.fsf@catnip.gol.com>
(restoring CC list. it is customary on the git list to reply-all)
On 2010-08-06 23:36, Miles Bader wrote:
> Conrad Parker <conrad@metadecks.org> writes:
>> Anyone interested in git-bzr might also want to look at some recent
>> rewrites; from the current git-bzr README:
>>
>> The following are rewrites in Python and may offer better bzr integration:
>> * http://github.com/termie/git-bzr-ng
>> * http://github.com/matthew-brett/git-bzr
>>
>> (... and I'd also be interested to know how well either of these work :)
I've found some time to begin implementing a remote-helper[1] this week.
Plugging in a call to "bzr fast-export" made cloning a repository with
"git clone bzr::url" and pulling new revisions in with "git pull" work
with minimum effort.
[1]:http://github.com/lelutin/git-remote-bzr
However, as reported in this bug[2], the fast-import path to push
commits back to bzr is broken in the bzr plugin. Once we get this
working, we should be able to round-trip.
[2]:https://bugs.launchpad.net/bzr-fastimport/+bug/347729
Doing "git pull" currently exports all history from the Bazaar branch to
incorporate the needed commits in the git repo. This is really
suboptimal, but I thought having something that works before making it
work right would help me get some insights on the remote-helper's code.
The very cool thing about making this into a remote-helper instead of a
git command in itself, is that we won't have to redisign (and possibly
re-implement) the command line interface, since git will be calling the
remote-helper with the right commands at the appropriate time.
--
Gabriel Filion
next prev parent reply other threads:[~2010-08-07 12:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 18:13 RFD: git-bzr: anyone interested? Gabriel Filion
2010-02-18 18:37 ` Sverre Rabbelier
2010-02-19 7:05 ` Gabriel Filion
2010-02-19 7:49 ` Sverre Rabbelier
2010-02-19 12:52 ` Gabriel
2010-02-19 13:38 ` Sverre Rabbelier
2010-02-19 15:15 ` Writing git remote helpers Gabriel
2010-02-22 4:53 ` RFD: git-bzr: anyone interested? Gabriel Filion
2010-02-19 13:55 ` Ilari Liusvaara
2010-02-22 4:42 ` Gabriel Filion
2010-02-22 10:51 ` Ilari Liusvaara
2010-02-23 3:20 ` Gabriel Filion
2010-02-23 12:45 ` Ilari Liusvaara
2010-04-26 21:41 ` Chris Packham
2010-04-26 23:46 ` Dmitrijs Ledkovs
2010-04-27 0:58 ` Chris Packham
2010-04-27 2:10 ` Miles Bader
2010-04-27 2:53 ` Gabriel Filion
2010-04-27 8:47 ` Dmitrijs Ledkovs
2010-04-27 17:00 ` Chris Packham
2010-04-27 17:13 ` Chris Packham
2010-04-27 23:22 ` Dmitrijs Ledkovs
2010-08-06 7:19 ` Conrad Parker
2010-08-07 3:36 ` Miles Bader
2010-08-07 8:48 ` Gabriel Filion [this message]
2010-08-07 13:37 ` Miles Bader
2010-08-07 13:03 ` git-archimport (was: Re: RFD: git-bzr: anyone interested?) Jakub Narebski
2010-08-07 13:11 ` git-archimport Matthieu Moy
2010-02-20 13:58 ` RFD: git-bzr: anyone interested? Felipe Contreras
2010-02-22 2:43 ` Gabriel Filion
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=4C5D1DC2.6000704@gmail.com \
--to=lelutin@gmail.com \
--cc=conrad@metadecks.org \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.com \
--cc=miles@gnu.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 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.