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

Re: [RFC/PATCH git] http: avoid empty error messages for some curl errors

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 6, 2011, 17:02 UTC
Message-ID
<7v62l5a9ke.fsf@alter.siamese.dyndns.org>
In-Reply-To
<alpine.DEB.2.00.1109061023010.3841@tvnag.unkk.fr>
Daniel Stenberg <daniel@haxx.se> writes:
Show 14 quoted lines
> On Mon, 5 Sep 2011, Jonathan Nieder wrote:
>
>> +			if (!curl_errorstr[0])
>> +				strlcpy(curl_errorstr,
>> +					curl_easy_strerror(results.curl_result),
>> +					sizeof(curl_errorstr));
>
> (as libcurl hacker)
>
> For the record, in libcurl we work on providing "extra" information in
> the error buffer when there is additional info to provide that would
> help. In some cases we deem there isn't (or we just to provide any)
> and then the generic error message is good enough and could indeed be
> used like this...
Sorry if I am a bit slow but are you saying:
 (1) we provide "extra" but your patch is not using it which is bad?
 (2) the above is Ok but there are better ways to do it?
 (3) something else?
Previous: Daniel StenbergNext: Daniel Stenberg
Message 4 of 6 in “http: avoid empty error messages for some curl errors”
  1. http: avoid empty error messages for some curl errorsJonathan Nieder, Sep 5, 2011
  2. http: remove extra newline in error messageJonathan Nieder, Sep 5, 2011
  3. Daniel StenbergSep 6, 2011
  4. Junio C HamanoSep 6, 2011
  5. Daniel StenbergSep 6, 2011
  6. Junio C HamanoSep 6, 2011

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.