From: James Cloos <cloos@jhcloos.com>
To: git@vger.kernel.org
Cc: Daniel Stenberg <daniel@haxx.se>
Subject: Re: git-fetch vs ipv6 routing issues
Date: Tue, 03 Jun 2008 19:56:01 -0400 [thread overview]
Message-ID: <m3prqygjiv.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <alpine.LRH.1.10.0806032242050.10782@yvahk3.pbagnpgbe.fr> (Daniel Stenberg's message of "Tue, 3 Jun 2008 22:50:16 +0200 (CEST)")
>>>>> "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
prev parent reply other threads:[~2008-06-03 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 17:56 git-fetch vs ipv6 routing issues James Cloos
2008-06-01 7:25 ` Daniel Stenberg
2008-06-03 19:53 ` James Cloos
2008-06-03 20:50 ` Daniel Stenberg
2008-06-03 23:56 ` James Cloos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3prqygjiv.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=daniel@haxx.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox