From: Sverre Rabbelier <srabbelier@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/8] Make the "traditionally-supported" URLs a special case
Date: Fri, 4 Sep 2009 19:14:53 +0200 [thread overview]
Message-ID: <fabb9a1e0909041014h3b2789d7i90115ac69368d442@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0909041114440.28290@iabervon.org>
Heya,
On Fri, Sep 4, 2009 at 17:40, Daniel Barkalow<barkalow@iabervon.org> wrote:
> As of this version, the idea is that there will be three ways helpers get
> selected:
How does this interact with wanting to support
"hg://example.org/example" by adding 'git-remote-hg' to you path? Does
it make that harder, or is it just not part of this series? I really
do think we should support that, and only resort to "svn::" or such if
the url is ambiguous (e.g., with a 'https://' prefix, etc).
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-09-04 17:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 2:13 [PATCH 1/8] Make the "traditionally-supported" URLs a special case Daniel Barkalow
2009-09-04 5:29 ` Sverre Rabbelier
[not found] ` <20090904172345.6117@nanako3.lavabit.com>
2009-09-04 10:47 ` Sverre Rabbelier
2009-09-04 15:40 ` Daniel Barkalow
2009-09-04 17:14 ` Sverre Rabbelier [this message]
2009-09-04 17:23 ` Junio C Hamano
2009-09-04 17:52 ` Sverre Rabbelier
2009-09-04 18:02 ` Johannes Schindelin
2009-09-04 19:05 ` Daniel Barkalow
2009-09-04 19:35 ` Sverre Rabbelier
2009-09-04 20:10 ` Daniel Barkalow
2009-09-04 21:08 ` Johannes Schindelin
2009-09-04 22:18 ` Daniel Barkalow
2009-09-04 22:36 ` Johannes Schindelin
2009-09-04 9:04 ` Mike Ralphson
2009-09-04 10:34 ` Johannes Schindelin
2009-09-04 10:50 ` Junio C Hamano
2009-09-04 12:33 ` Johannes Schindelin
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=fabb9a1e0909041014h3b2789d7i90115ac69368d442@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).