From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Gabriel Filion <lelutin@gmail.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: Mon, 29 Mar 2010 08:34:48 +0530 [thread overview]
Message-ID: <f3271551003282004h39ae8d95ma2bf6517e7d77d7b@mail.gmail.com> (raw)
In-Reply-To: <4BAFFFAB.4080808@gmail.com>
Hi,
> Oops, "needs" is repeated twice here...
Oops. Sorry about the silly mistake.
Junio: Could you please make this correction and apply the patch? I'm
writing another patch documenting invocation which depends on this
patch.
--- a/Documentation/git-remote-helpers.txt
+++ b/Documentation/git-remote-helpers.txt
@@ -15,7 +15,7 @@ DESCRIPTION
Remote helper programs are normally not used directly by end users,
but are invoked by git when it needs to interact with remote
repositories. They implement a subset of the capabilities documented
-here, and conform to the "remote helper protocol". When git needs
+here, and conform to the "remote helper protocol". When git
needs to interact with a repository served by a remote helper, it
spawns the helper as an independent process and interacts with it over
the specified protocol. Essentially, git sends commands to the helper
@@ -38,6 +38,51 @@ Git comes with a "curl" family of remote helpers,
specifically
'git-remote-ftps'. They implement the capabilities 'fetch', 'option',
and 'push'.
> http://lists.zerezo.com/git/msg712892.html
>
> Should we add this information on this man page?
Definitely. Thanks for pointing this out- I've already started
preparing a patch for this.
-- Ram
next prev parent reply other threads:[~2010-03-29 3:05 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
2010-03-29 3:04 ` Ramkumar Ramachandra [this message]
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=f3271551003282004h39ae8d95ma2bf6517e7d77d7b@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).