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

Re: [PATCH 3/3] Return CURL error message when object transfer fails

From
NHNick Hengeveld <nickh@reactrix.com>
Date
Sep 27, 2005, 00:12 UTC
Message-ID
<20050927001241.GB15615@reactrix.com>
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.
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “Return CURL error message when object transfer fails”
  1. 3/3 Return CURL error message when object transfer failsNick Hengeveld, Sep 26, 2005
  2. Junio C HamanoSep 26, 2005
  3. Nick HengeveldSep 27, 2005
  4. Junio C HamanoSep 27, 2005
  5. Junio C HamanoSep 27, 2005
  6. Nick HengeveldSep 27, 2005

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.