From: Gabriel Filion <lelutin@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git <git@vger.kernel.org>
Subject: Re: remote-bzr status
Date: Tue, 05 Oct 2010 21:24:45 -0400 [thread overview]
Message-ID: <4CABCFDD.4050902@gmail.com> (raw)
In-Reply-To: <AANLkTin_ziCLfsHOeqwzCSaAGWwxwUPi=1=4Hdhz7uSk@mail.gmail.com>
On 2010-10-04 14:07, Sverre Rabbelier wrote:
> On Mon, Oct 4, 2010 at 20:03, Gabriel Filion <lelutin@gmail.com> wrote:
>> My original plan was to try and make the helper work both ways, and then
>> to incorporate it into git.git to build patches on top of master (since
>> it's a new feature that should be working on the current master).
>
> It would be great if you could make it work by adding a bzr directory
> to git_remote_helpers and a git-remote-bzr.py to the root directory!
I have written a test file that uses test-lib.sh. It is named
t5801-remote-bzr.sh. I don't know if this name is right so I can correct
it. I simply took the next sequential number after t5800-remote-helpers.sh.
It is included in the repo mentioned earlier but it won't work in there..
I've created a clone of git.git [1] in which there's a 'remote-bzr'
branch. I will be rebasing this branch on top of master and keeping it
up to date with the other repo's content. (so most operations will be
non-fastforward pushes)
The previous repository will contain the detailed history about work on
the remote helper, while the git clone will contain a simple commit for
the helper, plus relevant commits for integration in git.git.
The test file can be used inside the git clone.
[1]: http://github.com/lelutin/git
Maintaining two repositories will add a little more work but it will
make it easier for me to post a series on top of git for review and
possible inclusion later.
Also, it should make it easier for interested people to test out the
remote helper, and to run the test file.
So now, most of my work will be to try and fix bzr-fastimport. I tried
to get in contact with current maintainers of the plugin via Bazaar's
mailing list but was unsuccessful. I guess I should e-mail Jelmer
Vernooij directly since he merged some code in not so long ago.
--
Gabriel Filion
next prev parent reply other threads:[~2010-10-06 1:24 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
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 [this message]
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=4CABCFDD.4050902@gmail.com \
--to=lelutin@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=srabbelier@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).