git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: advertised commit fetch using commit id fails

From
Jeff King <peff@peff.net>
Date
Jun 14, 2019, 15:29 UTC
Message-ID
<20190614152911.GC22984@sigill.intra.peff.net>
In-Reply-To
<20190614152710.GB22984@sigill.intra.peff.net>
On Fri, Jun 14, 2019 at 11:27:10AM -0400, Jeff King wrote:
> So in short, it was never supposed to work, but between bugs and
> protocol vagaries, there are a few version and protocol combinations
> where it did.

I'd add that in protocol v2, the reachability restrictions are lifted (i.e., every server behaves as if uploadpack.allowAnySHA1InWant is enabled). So you could probably just set protocol.version=2 on your client. This will eventually becomes the default, too.

-Peff
Previous: Jeff King
Message 3 of 3 in “advertised commit fetch using commit id fails”
  1. Karen ArutyunovJun 14, 2019
  2. Jeff KingJun 14, 2019
  3. Jeff KingJun 14, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.