From: Gabriel Filion <lelutin@gmail.com>
To: git <git@vger.kernel.org>
Subject: remote-bzr status
Date: Sun, 03 Oct 2010 17:17:37 -0400 [thread overview]
Message-ID: <4CA8F2F1.5090407@gmail.com> (raw)
Hi,
It's been a very long time now since I talked about this on the list.
The project (integration with Bazaar through a remote helper) is not
dead, it's just stalled because of bugs in the chosen "backend".
The remote helper code was done in python (mostly based off of Sverre's
remote-hg code) and relies on the "bzr-fastimport" tool. It can be found
on my github repository:
http://github.com/lelutin/git-remote-bzr
First off, what was done for now?
- The remote helper is able to pull in changes in Git repos and to
create tags.
- It is possible to push changes back _but_ only in some situations. The
"bzr-fastimport" tool currently has bugs [1] that prevent it from doing
what we want. I have included a patch in the remote helper repository to
fix one issue on the fix that was proposed but the whole thing is not
completely fixed.
[1]: https://bugs.launchpad.net/bzr-fastimport/+bug/347729
Why did I lag this much on this project?
Mostly because of lack of time. My $dayjob was far too demanding. But
since I am now self-employed, I want to find some time to work on this
and get it through.
I tried tinkering directly with "bzrlib" to make my own tool to
import/export information from/to Bazaar, but it is a tremendous PITA
(unstable API, bad documentation, exceptions thrown are not always easy
to understand).
I have been working on the bzr-fastimport bugs but I didn't receive any
feedback from maintainers. So I currently am wondering if I need to be
pushing for this tool to be fixed or if I should reimplement it.
Any help and/or support would be appreciated. I'll keep posting status
updates when I have new info or progress on the project.
--
Gabriel Filion
next reply other threads:[~2010-10-03 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 21:17 Gabriel Filion [this message]
2010-10-03 22:37 ` remote-bzr status Sverre Rabbelier
2010-10-04 6:11 ` Jonathan Nieder
2010-10-04 18:03 ` Gabriel Filion
2010-10-04 18:07 ` Sverre Rabbelier
2010-10-06 1:24 ` Gabriel Filion
2010-10-07 21:27 ` Sverre Rabbelier
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=4CA8F2F1.5090407@gmail.com \
--to=lelutin@gmail.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).