Adrian Ratiu says that while working on SHA-256 remote support in JJ, which uses Git for networking, he found no way to learn a repository's object format without cloning. Clone learns it during the protocol handshake, but it is not shown elsewhere. When fetching into an empty repository, a remote with refs can cause a mismatch error, and "git ls-remote" shows the format only indirectly through object ID length. If the remote is empty, ls-remote prints nothing and fetch succeeds, so the new local repo can silently get the wrong format, which shows up later.
Patrick Steinhardt reviewed the patch. He noted that guessing from hash length assumes Git never adds a third hash of the same length as an existing one. He suggested printing "object-format: %s" instead of a bare value, so that more fields can be added without making parsers depend on order. He also asked another question about the hash that is cut off in the excerpt. He pointed out a typo and said "repo" and "repository" appear awkwardly together in the text.
Ratiu agreed with the prefix idea and said he would send v2 addressing the feedback. He will wait about a week first to give others a chance to review.