[PATCH] Documentation: pack-protocol correct NAK response

Stefan Beller· Jul 22, 2016, 20:28 UTC · lore

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>
---
 Documentation/technical/pack-protocol.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 8b36343..d40ab65 100644
--- a/Documentation/technical/pack-protocol.txt
+++ b/Documentation/technical/pack-protocol.txt
@@ -307,7 +307,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:

-- 
2.9.2.370.g4a59376.dirty

Junio C Hamano· Jul 22, 2016, 20:31 UTC · re: Stefan Beller · lore

Re: [PATCH] Documentation: pack-protocol correct NAK response

On Fri, Jul 22, 2016 at 1:28 PM, Stefan Beller <sbeller@google.com> wrote:

> In the transport protocol we use NAK to signal the non existence of a
> common base, so fix the documentation.

Thanks.

patchDocumentation: pack-protocol correct NAK response