From: Gabriel Filion <lelutin@gmail.com>
To: git@vger.kernel.org
Subject: Re: RFD: git-bzr: anyone interested?
Date: Fri, 19 Feb 2010 02:05:58 -0500 [thread overview]
Message-ID: <4B7E3856.3080609@gmail.com> (raw)
In-Reply-To: <fabb9a1e1002181037n58d6942dpa63a57a23f506d9c@mail.gmail.com>
On 2010-02-18 13:37, Sverre Rabbelier wrote:
> By implementing a
> remote helper people can just clone a bzr url, and work with it in the
> exact same way that they would interact with a regular git repository.
This sounds great, it's exactly what I'm hoping to achieve with this
project.
> If you're interested have a look at
> Documentation/git-remote-helpers.txt, and read the mailing list
> archives on the subject.
>
The Documentation/git-remote-helpers.txt file wasn't really of much help
.. It really only barely scratches the subject, but it does not mention
how remote-helpers really work internally (e.g. how do they get called:
based on protocol used in URLs?)
I'm still trying to dig up information about how to actually build, test
and use a remote helper. I'll probably be reading code for examples.
Another detail hit me: external interaction in git seems like it's
almost always using librairies. If I'm not mistaken, bzr does not have a
separate library. So to have access to it's API, you need bzr to be
installed. This is why the current git-bzr script is using bzr +
bzr-fastimport plugin to do the job.
Is it normal / acceptable for a remote helper to have such dependancies?
And for the language used, maybe python could be logical if I can bind
directly to Bazaar's API. Tell me what you think about this.
--
Gabriel Filion
next prev parent reply other threads:[~2010-02-19 7:06 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 [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B7E3856.3080609@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).