From: Jeff King <peff@peff.net>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: CURLOPT_NOBODY
Date: Thu, 30 Apr 2015 16:13:21 -0400 [thread overview]
Message-ID: <20150430201321.GA7067@peff.net> (raw)
In-Reply-To: <CACnwZYeVVKrTDM5rTaZz9sTjQ9tjWsk52D8WMu8kDM3vxEiVLg@mail.gmail.com>
On Thu, Apr 30, 2015 at 04:57:28PM -0300, Thiago Farina wrote:
> The same logic you apply to CURLOPT_FILE -> CURLOPT_WRITEDATA?
Maybe. I had to track down the appropriate curl versions for the NOBODY
case manually. If you'd like to do the same for CURLOPT_FILE, be my
guest (and if it has always been that way, I do not mind a cleanup
patch).
-Peff
prev parent reply other threads:[~2015-04-30 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 2:20 CURLOPT_NOBODY Thiago Farina
2015-04-30 3:55 ` CURLOPT_NOBODY Jeff King
2015-04-30 19:57 ` CURLOPT_NOBODY Thiago Farina
2015-04-30 20:13 ` Jeff King [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=20150430201321.GA7067@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=tfransosi@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).