From: Sverre Rabbelier <srabbelier@gmail.com>
To: Gabriel Filion <lelutin@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: remote-bzr status
Date: Mon, 4 Oct 2010 00:37:25 +0200 [thread overview]
Message-ID: <AANLkTimbsxUJbZsadCxiw9MpicaND5g3db6fx=QtzaEY@mail.gmail.com> (raw)
In-Reply-To: <4CA8F2F1.5090407@gmail.com>
Heya,
> 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:
Glad you found my code helpful :).
> - 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.
I see you are not using the 'export' functionality, which is good
since it has a bug, but if you'd be interested in doing that, feel
free to ping me in #git-devel on freenode or on gchat, and we can
figure out what would be easiest.
> 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.
I'd recommend working on 'bzr fast-import', forking it if necessary.
Definitely preferable over creating a new tool from scratch.
> Any help and/or support would be appreciated. I'll keep posting status
> updates when I have new info or progress on the project.
Please keep up the good work, I'd love to be able to clone bzr repo's :).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-10-03 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 21:17 remote-bzr status Gabriel Filion
2010-10-03 22:37 ` Sverre Rabbelier [this message]
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='AANLkTimbsxUJbZsadCxiw9MpicaND5g3db6fx=QtzaEY@mail.gmail.com' \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=lelutin@gmail.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.
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).