From: Gabriel Filion <lelutin@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jonathan Nieder <jrnieder@gmail.com>,
Daniel Barkalow <barkalow@iabervon.org>,
Git Mailing List <git@vger.kernel.org>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Subject: Re: [PATCH v7 1/2] Documentation/remote-helpers: Rewrite description
Date: Sun, 28 Mar 2010 21:17:31 -0400 [thread overview]
Message-ID: <4BAFFFAB.4080808@gmail.com> (raw)
In-Reply-To: <f3271551003281103x68812b3cj806d6235965f0a32@mail.gmail.com>
Hello,
On 2010-03-28 14:03, Ramkumar Ramachandra wrote:
[...]
> diff --git a/Documentation/git-remote-helpers.txt
> b/Documentation/git-remote-helpers.txt
> index 1b5f61a..1304813 100644
> --- a/Documentation/git-remote-helpers.txt
> +++ b/Documentation/git-remote-helpers.txt
[...]
> @@ -12,11 +12,31 @@ SYNOPSIS
[...]
> +repositories. They implement a subset of the capabilities documented
> +here, and conform to the "remote helper protocol". When git needs
> +needs to interact with a repository served by a remote helper, it
Oops, "needs" is repeated twice here...
Apart from that, it seems nice and helps to better understand what they
should be used for.
It doesn't really concern this patch but If I'm not wrong, there still
is no documentation written on how exactly git invokes the remote
helpers. A good description was given previously by Ilari Liusvaara (so
I've added you, Ilari in the cc list). The description can be seen here:
http://lists.zerezo.com/git/msg712892.html
Should we add this information on this man page?
--
Gabriel Filion
next prev parent reply other threads:[~2010-03-29 1:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 18:03 [PATCH v7 1/2] Documentation/remote-helpers: Rewrite description Ramkumar Ramachandra
2010-03-29 1:17 ` Gabriel Filion [this message]
2010-03-29 3:04 ` Ramkumar Ramachandra
2010-03-29 3:08 ` Sverre Rabbelier
2010-03-29 5:09 ` Daniel Barkalow
2010-03-29 6:18 ` Ramkumar Ramachandra
2010-03-29 6:39 ` Jonathan Nieder
2010-03-29 15:39 ` Daniel Barkalow
2010-03-30 3:23 ` Ramkumar Ramachandra
2010-03-29 3:25 ` Tay Ray Chuan
2010-03-29 3:45 ` Ramkumar Ramachandra
2010-04-05 14:05 ` Ramkumar Ramachandra
2010-04-05 21:55 ` Junio C Hamano
2010-04-06 2:47 ` Ramkumar Ramachandra
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=4BAFFFAB.4080808@gmail.com \
--to=lelutin@gmail.com \
--cc=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=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).