From: Nick Hengeveld <nickh@reactrix.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/3] Return CURL error message when object transfer fails
Date: Mon, 26 Sep 2005 17:12:41 -0700 [thread overview]
Message-ID: <20050927001241.GB15615@reactrix.com> (raw)
In-Reply-To: <7v4q87ed73.fsf@assigned-by-dhcp.cox.net>
On Mon, Sep 26, 2005 at 02:22:56PM -0700, Junio C Hamano wrote:
> Sounds like a good idea. Also if you happen to know if this
> option is not available in older versions of the library, it
> might not hurt to guard it with "#if LIBCURL_VERSION_NUM" like
> we do with other options.
I don't see any indication that CURLOPT_ERRORBUFFER is a new feature.
The curl_easy_strerror() function is new as of 7.12.0 which is why
I elected to use the CURLOPT_ERRORBUFFER option instead.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
next prev parent reply other threads:[~2005-09-27 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 17:52 [PATCH 3/3] Return CURL error message when object transfer fails Nick Hengeveld
2005-09-26 21:22 ` Junio C Hamano
2005-09-27 0:12 ` Nick Hengeveld [this message]
2005-09-27 5:51 ` Junio C Hamano
2005-09-27 6:13 ` Junio C Hamano
2005-09-27 16:07 ` Nick Hengeveld
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=20050927001241.GB15615@reactrix.com \
--to=nickh@reactrix.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.