summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2013-07-24 08:01:21 (GMT)
committerJunio C Hamano <gitster@pobox.com>2013-07-24 22:57:01 (GMT)
commit9a621ad085c646a0146cc073fcc8dc49b89f574a (patch)
treeaecf64e40270e0481171bb5f74a72024ddc88769
parent15999998fbda60552742275570947431b57108ae (diff)
downloadgit-9a621ad085c646a0146cc073fcc8dc49b89f574a.zip
git-9a621ad085c646a0146cc073fcc8dc49b89f574a.tar.gz
git-9a621ad085c646a0146cc073fcc8dc49b89f574a.tar.bz2
docs: fix 'report-status' protocol capability thinko
The report-status capability is understood by receive-pack, not upload-pack. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/technical/protocol-capabilities.txt2
1 files changed, 1 insertions, 1 deletions
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 @@ of whether or not there are tags available.
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