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

RFC Failover url for fetches?

From
Stefan Beller <sbeller@google.com>
Date
Oct 21, 2016, 18:19 UTC
Message-ID
<CAGZ79kaPdSfY_DXL6BDQ9pAma8p61r4m1n81VTxPHYi8zQuZfA@mail.gmail.com>

So when pushing it is possible to have multiple urls (remote.<name>.url) configured.

When fetching only the first configured url is considered. Would it make sense to allow multiple urls and try them one by one until one works?

Background: http://www.businessinsider.com/amazon-spotify-twitter-github-and-etsy-down-in-apparent-dns-attack-2016-10

I wanted to fetch and had to fix a url of a repo to point to a working mirror.

Thanks, Stefan

Next: Junio C Hamano
Message 1 of 4 in “RFC Failover url for fetches?”
  1. Stefan BellerOct 21, 2016
  2. Junio C HamanoOct 21, 2016
  3. Jakub NarębskiOct 23, 2016
  4. Junio C HamanoOct 24, 2016

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.