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

Re: [PATCH 1/2] imap-send.c: implements the GIT_CURL_DEBUG environment variable

From
Elia Pinto <gitter.spiros@gmail.com>
Date
Apr 4, 2016, 16:08 UTC
Message-ID
<CA+EOSBkY-Tsz3ZAfK3uAXJsrE585cOhyxjsU4FhgDMFC-ypkUg@mail.gmail.com>
In-Reply-To
<xmqqtwjljq97.fsf@gitster.mtv.corp.google.com>
2016-04-01 17:35 GMT+02:00 Junio C Hamano <gitster@pobox.com>:
Show 11 quoted lines
> Elia Pinto <gitter.spiros@gmail.com> writes:
>
>> Implements the GIT_CURL_DEBUG environment variable to allow a greater
>> degree of detail of GIT_CURL_VERBOSE, in particular the complete
>> transport header and all the data payload exchanged.
>> It might be useful if a particular situation could require a more
>> thorough debugging analysis.
>
> My impression is that using GIT_TRACE_* is the more mainstream
> trend, and it may be beneficial to work any new debugging aid like
> this one to fit within that mechanism.
I thought about it, and I agree with you. The idea could be
- Call the variable GIT_TRACE_CURL_DEBUG instead
- Add the new GIT_TRACE_CURL_VERBOSE variable, keeping
GIT_CURL_VERBOSE for compatibility
- Documenting these GIT_TRACE_CURL_XXX variables (GIT_CURL_VERBOSE
it is not even documented i think)
- perhaps use the git trace api in doing these new patches
Look reasonable? It seems reasonable? I'd like your own opinion
Thank you for your suggestion
Show 5 quoted lines
>
> I am not saying new GIT_*_DEBUG is wrong.  I just wanted to make
> sure you have considered doing this as a new trace in GIT_TRACE_*
> family and rejected that apporach with a very good reason, in
> which case that rationale deserves to be in the log message.
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 14 in “imap-send.c: implements the GIT_CURL_DEBUG environment variable”
  1. 1/2 imap-send.c: implements the GIT_CURL_DEBUG environment variableElia Pinto, Apr 1, 2016
  2. 2/2 http.c: implements the GIT_CURL_DEBUG environment variableElia Pinto, Apr 1, 2016
  3. Ramsay JonesApr 1, 2016
  4. Elia PintoApr 4, 2016
  5. Torsten BögershausenApr 1, 2016
  6. Ramsay JonesApr 1, 2016
  7. Elia PintoApr 4, 2016
  8. Junio C HamanoApr 1, 2016
  9. Elia PintoApr 4, 2016
  10. Junio C HamanoApr 4, 2016
  11. Eric SunshineApr 1, 2016
  12. Elia PintoApr 5, 2016
  13. Eric SunshineApr 6, 2016
  14. Jeff KingApr 6, 2016

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.