protocol-capabilities.txt: clarify "allow-x-sha1-in-want" re SHA-256
Two of our capabilities contain "sha1" in their names, but that's historical. Clarify that object names are still to be given using whatever object format has been negotiated using the "object-format" capability. Signed-off-by: Martin Ågren <martin.agren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Martin Ågren committed
Aug 15, 2020 at 18:06 UTC
0756e61078b32686dc995df768e50725aba13b7e
1 file changed
+8
-4
Documentation/technical/protocol-capabilities.txt
+8
-4
@@ -324,15 +324,19 @@ allow-tip-sha1-in-want
324
----------------------
325
326
If the upload-pack server advertises this capability, fetch-pack may
327
-send "want" lines with SHA-1s that exist at the server but are not
328
-advertised by upload-pack.
327
+send "want" lines with object names that exist at the server but are not
328
+advertised by upload-pack. For historical reasons, the name of this
329
+capability contains "sha1". Object names are always given using the
330
+object format negotiated through the 'object-format' capability.
331
332
allow-reachable-sha1-in-want
333
----------------------------
334
335
If the upload-pack server advertises this capability, fetch-pack may
334
-send "want" lines with SHA-1s that exist at the server but are not
335
-advertised by upload-pack.
336
+send "want" lines with object names that exist at the server but are not
337
+advertised by upload-pack. For historical reasons, the name of this
338
+capability contains "sha1". Object names are always given using the
339
+object format negotiated through the 'object-format' capability.
340
341
push-cert=<nonce>
342
-----------------