[PATCH v2 1/4] http-protocol.txt: document SHA-256 "want"/"have" format
- From
- Martin Ågren <martin.agren@gmail.com>
- Date
- Aug 15, 2020, 16:05 UTC
- Message-ID
- <2e9f6b92946dc2fa645adc72f32d5d05a1720185.1597506837.git.martin.agren@gmail.com>
- In-Reply-To
- <cover.1597506837.git.martin.agren@gmail.com>
Document that rather than always naming objects using SHA-1, we should use whatever has been negotiated using the object-format capability.
Signed-off-by: Martin Ågren <martin.agren@gmail.com> --- Documentation/technical/http-protocol.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/technical/http-protocol.txt b/Documentation/technical/http-protocol.txt index 51a79e63de..96d89ea9b2 100644 --- a/Documentation/technical/http-protocol.txt +++ b/Documentation/technical/http-protocol.txt @@ -401,8 +401,9 @@ at all in the request stream: The stream is terminated by a pkt-line flush (`0000`). A single "want" or "have" command MUST have one hex formatted -SHA-1 as its value. Multiple SHA-1s MUST be sent by sending -multiple commands. +object name as its value. Multiple object names MUST be sent by sending +multiple commands. Object names MUST be given using the object format +negotiated through the `object-format` capability (default SHA-1). The `have` list is created by popping the first 32 commits from `c_pending`. Less can be supplied if `c_pending` empties.
-- 2.28.0.297.g1956fa8f8d