diff options
| author | Stefan Beller <sbeller@google.com> | 2016-07-22 13:28:20 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2016-07-22 13:31:55 -0700 |
| commit | 280abfd4f5055922e8abcbb988fa0a8df0eef128 (patch) | |
| tree | 650549f25b3b3d1a800d9389127519996bbde19b | |
| parent | 765428699a5381f113d19974720bc91b5bfeaf1d (diff) | |
| download | git-sb/pack-protocol-doc-nak.tar.gz | |
Documentation: pack-protocol correct NAK responsesb/pack-protocol-doc-nak
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>
| -rw-r--r-- | Documentation/technical/pack-protocol.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt index 4064fc796f..49d6ed0850 100644 --- a/Documentation/technical/pack-protocol.txt +++ b/Documentation/technical/pack-protocol.txt @@ -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: |