From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Gabriel Filion <lelutin@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jonathan Nieder <jrnieder@gmail.com>,
Daniel Barkalow <barkalow@iabervon.org>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
Tay Ray Chuan <rctay89@gmail.com>
Subject: [PATCH 2/2] Documentation/remote-helpers: Clarify "curl" family of remote helpers
Date: Mon, 29 Mar 2010 09:34:58 +0530 [thread overview]
Message-ID: <f3271551003282104m1c273450pacc5d5c84125fa54@mail.gmail.com> (raw)
Rewrite paragraph about "curl" family of remote helpers to clarify
different invocations of the same program.
---
Documentation/git-remote-helpers.txt | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-remote-helpers.txt
b/Documentation/git-remote-helpers.txt
index 58533e5..f1fc736 100644
--- a/Documentation/git-remote-helpers.txt
+++ b/Documentation/git-remote-helpers.txt
@@ -33,10 +33,9 @@ reachable via those refs to local, and update the
local object
store. Using the 'push' capability, they can transfer objects from
local to remote, and update the corresponding refs as necessary.
-Git comes with a "curl" family of remote helpers, specifically
-'git-remote-http', 'git-remote-https', 'git-remote-ftp' and
-'git-remote-ftps'. They implement the capabilities 'fetch', 'option',
-and 'push'.
+Git comes with a "curl" remote helper, which can be invoked as
+'git-remote-http', 'git-remote-https', 'git-remote-ftp' or
+'git-remote-ftps'. See INVOCATION below.
INVOCATION
----------
--
1.7.0.3
next reply other threads:[~2010-03-29 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 4:04 Ramkumar Ramachandra [this message]
2010-03-29 6:53 ` [PATCH 2/2] Documentation/remote-helpers: Clarify "curl" family of remote helpers Junio C Hamano
2010-03-29 7:14 ` 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=f3271551003282104m1c273450pacc5d5c84125fa54@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=rctay89@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).