Documentation: pack-protocol correct NAK response
authorStefan Beller <sbeller@google.com>
Fri, 22 Jul 2016 20:28:20 +0000 (13:28 -0700)
committerJunio C Hamano <gitster@pobox.com>
Fri, 22 Jul 2016 20:31:55 +0000 (13:31 -0700)
In the transport protocol we use NAK to signal the non existence of a
common base, so fix the documentation. This helps readers of the document,
as they don't have to wonder about the difference between NAK and NACK.
As NACK is used in git archive and upload-archive, this is easy to get
wrong.

Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/technical/pack-protocol.txt
index 4064fc796fe36e58eb580de2c66a00196051ba5f..49d6ed0850d42837ac9b78adb0f12b48abbe04fa 100644 (file)
@@ -302,7 +302,7 @@ In multi_ack mode:
     ready to make a packfile, it will blindly ACK all 'have' obj-ids
     back to the client.
 
-  * the server will then send a 'NACK' and then wait for another response
+  * the server will then send a 'NAK' and then wait for another response
     from the client - either a 'done' or another list of 'have' lines.
 
 In multi_ack_detailed mode: