From: Jeff King <peff@peff.net>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Clemens Buchacher <drizzd@aon.at>,
Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 1/4] docs: fix 'report-status' protocol capability thinko
Date: Wed, 24 Jul 2013 04:01:21 -0400 [thread overview]
Message-ID: <20130724080120.GA4425@sigill.intra.peff.net> (raw)
In-Reply-To: <20130724080051.GA3890@sigill.intra.peff.net>
The report-status capability is understood by receive-pack,
not upload-pack.
Signed-off-by: Jeff King <peff@peff.net>
---
Documentation/technical/protocol-capabilities.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/technical/protocol-capabilities.txt b/Documentation/technical/protocol-capabilities.txt
index b15517f..11467ff 100644
--- a/Documentation/technical/protocol-capabilities.txt
+++ b/Documentation/technical/protocol-capabilities.txt
@@ -168,7 +168,7 @@ report-status
report-status
-------------
-The upload-pack process can receive a 'report-status' capability,
+The receive-pack process can receive a 'report-status' capability,
which tells it that the client wants a report of what happened after
a packfile upload and reference update. If the pushing client requests
this capability, after unpacking and updating references the server
--
1.8.3.rc1.30.gff0fb75
next prev parent reply other threads:[~2013-07-24 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 12:25 Missing capabilities in Documentation/technical/protocol-capbilities.txt Duy Nguyen
2013-07-17 11:31 ` Clemens Buchacher
2013-07-24 8:00 ` [PATCH 0/4] protocol-capabilities documentation updates Jeff King
2013-07-24 8:01 ` Jeff King [this message]
2013-07-24 8:01 ` [PATCH 2/4] docs: note that receive-pack knows side-band-64k capability Jeff King
2013-07-24 8:03 ` [PATCH 3/4] document 'agent' protocol capability Jeff King
2013-07-24 8:03 ` [PATCH 4/4] document 'quiet' receive-pack capability Jeff King
2013-07-26 11:01 ` [PATCH 5/4] document 'allow-tip-sha1-in-want' capability Nguyễn Thái Ngọc Duy
2013-07-26 15:36 ` Junio C Hamano
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=20130724080120.GA4425@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).