pack-protocol.txt: clarify 'obj-id' in the last ACK after 'done'
It's introduced in 1bd8c8f (git-upload-pack: Support the multi_ack protocol - 2005-10-28) but probably better documented in the commit message of 78affc4 (Add multi_ack_detailed capability to fetch-pack/upload-pack - 2009-10-30). Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Nguyễn Thái Ngọc Duy committed
Feb 6, 2014 at 22:10 UTC
32752e966d3370f6b411b42fe3a301bbd46d3eae
1 file changed
+2
-1
Documentation/technical/pack-protocol.txt
+2
-1
@@ -338,7 +338,8 @@ during a prior round. This helps to ensure that at least one common
338
ancestor is found before we give up entirely.
339
340
Once the 'done' line is read from the client, the server will either
341
-send a final 'ACK obj-id' or it will send a 'NAK'. The server only sends
341
+send a final 'ACK obj-id' or it will send a 'NAK'. 'obj-id' is the object
342
+name of the last commit determined to be common. The server only sends
343
ACK after 'done' if there is at least one common base and multi_ack or
344
multi_ack_detailed is enabled. The server always sends NAK after 'done'
345
if there is no common base found.