From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: Gabriel Filion <lelutin@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: RFD: git-bzr: anyone interested?
Date: Tue, 23 Feb 2010 14:45:53 +0200 [thread overview]
Message-ID: <20100223124553.GA19153@Knoppix> (raw)
In-Reply-To: <4B834989.50502@gmail.com>
On Mon, Feb 22, 2010 at 10:20:41PM -0500, Gabriel Filion wrote:
> On 2010-02-22 05:51, Ilari Liusvaara wrote:
> > bzr::ssh://something/somewhere ?
> >
> > That goes to git-remote-bzr (as 'ssh://something/somewhere').
> >
> That would be feasible. But for users, when they copy URLs from sites,
> they'd probably like to use it as is. (I'd like it to be like that :P )
>
> But, as long as it's not possible right now to use "+" in the URL, I can
> implement it exactly like you said and maybe change it later if helper
> names obtain the right to have non-alnum characters.
Patch to allow '+', '-' and '.' sent (those characters were taken from
IETF STD66).
Its entierely possible to have remote helpers set up so that in git
version that doesn't allow '+', the following work (passed as means
beginning of second (URL) argument):
1) 'bzr://' [passed as 'bzr://']
2) 'bzr::ssh://' [passed as 'ssh://']
And in versions that allow '+', the following additionally work:
3) 'bzr+ssh://' [passed as 'bzr+ssh://']
4) 'ssh+bzr://' [passed as 'ssh+bzr://']
That can be done by making three copies of executable ('git-remote-bzr',
'git-remote-bzr+ssh' and 'git-remote-ssh+bzr') and the infering correct
protocol from prefix of 2nd arguement (see those "passed as" strings).
-Ilari
next prev parent reply other threads:[~2010-02-23 12:46 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 [this message]
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=20100223124553.GA19153@Knoppix \
--to=ilari.liusvaara@elisanet.fi \
--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.
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).