"brian m. carlson" <sandals@xxxxxxxxxxxxxxxxxxxx> writes:
> From: "brian m. carlson" <bk2204@xxxxxxxxxx>
>
> When cloning an empty repository, the HTTP protocol version 0 currently
> offers nothing but the header and flush packets for the /info/refs
> endpoint. This means that no capabilities are provided, so the client
> side doesn't know what capabilities are present.
>
> However, this does pose a problem when working with SHA-256
> repositories, since we use the capabilities to know the remote side's
> object format (hash algorithm). It used to be possible to set the
> correct algorithm with `GIT_DEFAULT_HASH` (which is what the Git LFS
> testsuite did), but this no longer works as of 8b214c2e9d ("clone:
"this no longer works as of" -> "this was a mistake and was fixed by".
> propagate object-format when cloning from void", 2023-04-05), since
> there we always read the hash algorithm from the remote. If there is no
> hash algorithm provided, we default to SHA-1 for backwards
> compatibility.
Other than that, looks good to me.
Thanks. Will queue.
