threads / patch / 23324

patch, 2 partspack-protocol.txt: fix spelling

Subject: [PATCH 1/2] pack-protocol.txt: fix spelling

## tl;dr

2 messages between Apr 4, 2010 and Apr 4, 2010. Diffs are folded; open one to read it.

replies: 1people: 1as markdown or json

Tay Ray Chuan· Apr 4, 2010, 13:12 UTC · lore
s/paramater/parameter/.
Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
---
 Documentation/technical/pack-protocol.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
Show changes to Documentation/technical/pack-protocol.txt +1 −1
diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
index 9a5cdaf..f9468a1 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
 
-- 
1.7.0.20.gcb44ed
Tay Ray Chuan· Apr 4, 2010, 13:12 UTC · re: Tay Ray Chuan · lore

[PATCH 2/2] pack-protocol.txt: fix pkt-line lengths

Previously, the lengths were 4-bytes short. Fix it such that the lengths reflect the total length of the pkt-line, as per spec.

Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
---
 Documentation/technical/pack-protocol.txt |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
Show changes to Documentation/technical/pack-protocol.txt +4 −4
diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
index f9468a1..369f91d 100644
--- a/Documentation/technical/pack-protocol.txt
+++ b/Documentation/technical/pack-protocol.txt
@@ -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
 ----
-- 
1.7.0.20.gcb44ed

← back to recent threads