summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2010-04-04 10:23:21 -0700
committerJunio C Hamano <gitster@pobox.com>2010-04-04 10:23:21 -0700
commit11766ca4a89ba960271e94281463d1b44654ca3b (patch)
tree6d6b47f34c698830b9faf66968938c3490c5ac51
parent9234b003726556e0d3d0ea8ade97dc9f7bd50a6e (diff)
parentc8a97906bad44c83acfec33e7e0a3bb4b15a716d (diff)
downloadgit-11766ca4a89ba960271e94281463d1b44654ca3b.tar.gz
Merge branch 'maint'
* maint: pack-protocol.txt: fix pkt-line lengths pack-protocol.txt: fix spelling
-rw-r--r--Documentation/technical/pack-protocol.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
index 9a5cdafa9c..369f91d3b9 100644
--- a/Documentation/technical/pack-protocol.txt
+++ b/Documentation/technical/pack-protocol.txt
@@ -36,7 +36,7 @@ Git Transport
The Git transport starts off by sending the command and repository
on the wire using the pkt-line format, followed by a NUL byte and a
-hostname paramater, terminated by a NUL byte.
+hostname parameter, terminated by a NUL byte.
0032git-upload-pack /project.git\0host=myserver.com\0
@@ -331,7 +331,7 @@ An incremental update (fetch) response might look like this:
C: 0009done\n
- S: 003aACK 74730d410fcb6603ace96f1dc55ea6196122532d\n
+ S: 0031ACK 74730d410fcb6603ace96f1dc55ea6196122532d\n
S: [PACKFILE]
----
@@ -488,7 +488,7 @@ An example client/server communication might look like this:
C: 0000
C: [PACKDATA]
- S: 000aunpack ok\n
- S: 0014ok refs/heads/debug\n
- S: 0026ng refs/heads/master non-fast-forward\n
+ S: 000eunpack ok\n
+ S: 0018ok refs/heads/debug\n
+ S: 002ang refs/heads/master non-fast-forward\n
----