From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
Daniel Barkalow <barkalow@iabervon.org>,
Gabriel Filion <lelutin@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v2] Documentation/remote-helpers: Add invocation section
Date: Wed, 31 Mar 2010 02:12:44 +0530 [thread overview]
Message-ID: <f3271551003301342j2fcefee6l1e9c9fa2d012bc11@mail.gmail.com> (raw)
In-Reply-To: <20100330202511.GC10977@progeny.tock>
Hi,
On Wed, Mar 31, 2010 at 1:55 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hmm. urls.txt is not currently its own page; instead, it is included
> in git-clone(1) and so on. I hope to change that this weekend.
My thoughts exactly. The giturls(7) idea will have to be dropped. It
looks like we have to post a patch for urls.txt to include some
introductory text and turn it into giturls(1), a manpage in its own
right. Then we have to remove references to urls.txt from all the
documents and make them point to gituls(1). I suspect the whole thing
will have to be done bit by bit, and go through several reviews. I can
help out a bit, but I wait for you to write most of it first.
One very realistic problem: Ambiguity between general URLS, "URLS
recognized by Git", and "arbitrary strings that perform the same
function as URLS".
> More to the point, wouldn’t "URL recognized by Git" mean a string
> like fd::3,4 rather than the 3,4 that is passed to ‘git remote-fd’?
That falls under the <transport>::<address> category, but Ilari might
very well come up with a totally new syntax for a remote helper he
writes tomorrow.
> Also worth keeping in mind: we want to support third-party helpers, too.
> So it is hard to have one centralized document that completely explains
> all possible URLs.
Okay, I'll try to word it accordingly then. "URLS recognized by git,
and arbitrary URL-like strings recognized by that specific remote
helper program".
-- Ram
prev parent reply other threads:[~2010-03-30 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:47 [PATCH v2] Documentation/remote-helpers: Add invocation section Ramkumar Ramachandra
2010-03-30 18:37 ` Jonathan Nieder
2010-03-30 19:17 ` Ramkumar Ramachandra
2010-03-30 19:59 ` Jonathan Nieder
2010-03-30 20:10 ` Ilari Liusvaara
2010-03-30 20:15 ` Ramkumar Ramachandra
2010-03-30 20:25 ` Jonathan Nieder
2010-03-30 20:42 ` Ramkumar Ramachandra [this message]
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=f3271551003301342j2fcefee6l1e9c9fa2d012bc11@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ilari.liusvaara@elisanet.fi \
--cc=jrnieder@gmail.com \
--cc=lelutin@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).