commit 2240b5a6621e136318f2cc301f097231f93b1d478bdba046799957167978f096 from: Stefan Sperling date: Fri Jan 30 11:12:36 2026 UTC sha256 network support can in fact be implemented on top of Git protocol v1 pointed by Runxi Yu on IRC, thanks! commit - b5a1fa8b33f6560a3b41876ccce5030693e75b09ee2efcd53952967bf1ef37d7 commit + 2240b5a6621e136318f2cc301f097231f93b1d478bdba046799957167978f096 blob - 98ff7c4f25bcd097e31abe74db869e1decee9ad8dc8470012e0ee93ef3611783 blob + 97301a601d50872d89d2b60c64e10475864a8a41c313d98b913d53f8d48274c1 --- got/got.1 +++ got/got.1 @@ -4496,7 +4496,7 @@ With repositories that use the sha256 object ID hashin is currently required for all network operations (clone, fetch, and push) because .Nm -does not yet support version 2 of the Git network protocol. +does not yet support the object-format capability of the Git network protocol. .It Writing to remote repositories over HTTP or HTTPS protocols requires .Xr git-push 1 . blob - 82f50f742b8e7540f37b6e99f711d83a57166fb0b60831b523fc2b41e28898de blob + 3db7aa9e8772d148dfb7c5695892fb7a70c5f0690f6c7ae51d41fe2a2fa5cd2f --- gotd/gotd.8 +++ gotd/gotd.8 @@ -125,7 +125,7 @@ At present, cannot serve repositories that use the sha256 object ID hashing algorithm because .Nm -does not yet support version 2 of the Git network protocol. +does not yet support the object-format capability of the Git network protocol. .Pp .Nm cannot honour the SIGHUP signal because the