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

Re: git-fetch vs ipv6 routing issues

From
James Cloos <cloos@jhcloos.com>
Date
Jun 3, 2008, 23:56 UTC
Message-ID
<m3prqygjiv.fsf@lugabout.jhcloos.org>
In-Reply-To
<alpine.LRH.1.10.0806032242050.10782@yvahk3.pbagnpgbe.fr>
>>>>> "Daniel" == Daniel Stenberg <daniel@haxx.se> writes:

Daniel> Eeek. I really disagree with this suggestion. CURLOPT_CONNECT_ONLY Daniel> means you only (TCP or over proxy) connect and nothing more. That Daniel> would force git to implement a lot of HTTP details that libcurl Daniel> already provides.

OK.  Then I misread that section of the curl_easy_setopt(3) man page.

I do think git should be able to do this even when compiled against legacy versions of libcurl, though.

(Of course, even better would be the ability to aviod http altogether. But some projects I track are only available via http urls....)

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6
Previous: Daniel Stenberg
Message 5 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.