Documentation: pack-protocol correct NAK response
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>
Stefan Beller committed
Jul 22, 2016 at 13:28 UTC
280abfd4f5055922e8abcbb988fa0a8df0eef128
1 file changed
+1
-1
Documentation/technical/pack-protocol.txt
+1
-1
@@ -302,7 +302,7 @@ In multi_ack mode:
302
ready to make a packfile, it will blindly ACK all 'have' obj-ids
303
back to the client.
304
305
- * the server will then send a 'NACK' and then wait for another response
305
+ * the server will then send a 'NAK' and then wait for another response
306
from the client - either a 'done' or another list of 'have' lines.
307
308
In multi_ack_detailed mode: