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

Re: git-fetch vs ipv6 routing issues

From
Daniel Stenberg <daniel@haxx.se>
Date
Jun 1, 2008, 07:25 UTC
Message-ID
<alpine.LRH.1.10.0806010924340.27605@yvahk3.pbagnpgbe.fr>
In-Reply-To
<m38wxq1hou.fsf@eagle.jhcloos.com>
On Sat, 31 May 2008, James Cloos wrote:
> I just noticed that, given a remote URL with a hostname which has both A and 
> AAAA RRs in the DNS, git-fetch will retry a git-protocol fetch using the v4 
> address if the v6 address is unreachable, but will not do so when the remote 
> is an http URL.

Isn't this simply because libcurl (used for http) has no retry functionality on this scenario while git itself has that for the git protocol?

-- 
  / daniel.haxx.se
Previous: James CloosNext: James Cloos
Message 2 of 5 in “git-fetch vs ipv6 routing issues”
  1. James CloosMay 31, 2008
  2. Daniel StenbergJun 1, 2008
  3. James CloosJun 3, 2008
  4. Daniel StenbergJun 3, 2008
  5. James CloosJun 3, 2008

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.