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

Re: [PATCH] curl: add support for curl_global_trace() components

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Aug 27, 2025, 09:21 UTC
Message-ID
<57a79b29-0e65-482c-b0a8-1e73744ad5f6@app.fastmail.com>
In-Reply-To
<20250827080702.GA3572995@coredump.intra.peff.net>
On Wed, Aug 27, 2025, at 10:07, Jeff King wrote:
> This patch teaches Git's http code to accept a component list from the
> environment and pass it into curl_global_trace(). We can then use that
> in the test to enable the correct component.
s/This patch teaches Git's http code/Teach Git's http code/
SubmittingPatches “imperative-mood”
Show 14 quoted lines
>
> It should be safe to do so unconditionally. In older versions of curl
> which don't support this call, setting the environment variable is a
> noop. Likewise, any versions of curl which don't recognize the "socks"
> component should silently ignore it. The manpage for curl_global_trace()
> says this:
>
>   The config string is a list of comma-separated component names. Names
>   are case-insensitive and unknown names are ignored. The special name
>   "all" applies to all components. Names may be prefixed with '+' or '-'
>   to enable or disable detailed logging for a component.
>
>   The list of component names is not part of curl's public API. Names may
>   be added or disappear in future ver‐ sions of libcurl. Since unknown
s/ver‐ sions/versions/
>   names are silently ignored, outdated log configurations does not cause
>   errors when upgrading libcurl. Given that, some names can be expected
>   to be fairly stable and are listed below for easy reference.
>[snip]
-- 
Kristoffer Haugsbakk
Previous: Jeff KingNext: Jeff King
Message 2 of 3 in “curl: add support for curl_global_trace() components”
  1. curl: add support for curl_global_trace() componentsJeff King, Aug 27, 2025
  2. Kristoffer HaugsbakkAug 27, 2025
  3. Jeff KingAug 30, 2025

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.