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

RFC: Would a config fetch.retryCount make sense?

From
Lars Schneider <larsxschneider@gmail.com>
Date
Jun 1, 2017, 12:48 UTC
Message-ID
<6762A30E-C558-4085-943B-AB85EBF18706@gmail.com>
Hi,

we occasionally see "The remote end hung up unexpectedly" (pkt-line.c:265) on our `git fetch` calls (most noticeably in our automations). I expect random network glitches to be the cause.

In some places we added a basic retry mechanism and I was wondering if this could be a useful feature for Git itself.

E.g. a Git config such as "fetch.retryCount" or something. Or is there something like this in Git already and I missed it?

Thanks, Lars

Next: Ben Peart
Message 1 of 5 in “RFC: Would a config fetch.retryCount make sense?”
  1. Lars SchneiderJun 1, 2017
  2. Ben PeartJun 1, 2017
  3. Lars SchneiderJun 5, 2017
  4. Ben PeartJun 5, 2017
  5. Stefan BellerJun 1, 2017

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.