aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-08-19 14:23:55 -0700
committerJunio C Hamano <gitster@pobox.com>2014-09-15 13:23:20 -0700
commite543b3f6fee9f910573d53ddfc0750cd2bf88972 (patch)
tree829f22abe40c35168a5d72f016b13233e7fbe36e
parentd7c67668fe10184736bdfe953ed8dcbfdb57e0c2 (diff)
downloadgit-e543b3f6fee9f910573d53ddfc0750cd2bf88972.tar.gz
git-e543b3f6fee9f910573d53ddfc0750cd2bf88972.tar.xz
pack-protocol doc: typofix for PKT-LINE
Everywhere else we use PKT-LINE to denote the pkt-line formatted data, but "shallow/deepen" messages are described with PKT_LINE(). Fix them. Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/technical/pack-protocol.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
index 18dea8d15..a845d51b1 100644
--- a/Documentation/technical/pack-protocol.txt
+++ b/Documentation/technical/pack-protocol.txt
@@ -212,9 +212,9 @@ out of what the server said it could do with the first 'want' line.
want-list = first-want
*additional-want
- shallow-line = PKT_LINE("shallow" SP obj-id)
+ shallow-line = PKT-LINE("shallow" SP obj-id)
- depth-request = PKT_LINE("deepen" SP depth)
+ depth-request = PKT-LINE("deepen" SP depth)
first-want = PKT-LINE("want" SP obj-id SP capability-list LF)
additional-want = PKT-LINE("want" SP obj-id LF)