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

[PATCHv3 1/3] git.txt: document the new GIT_TRACE_CURL environment variable

From
Elia Pinto <gitter.spiros@gmail.com>
Date
Apr 20, 2016, 16:28 UTC
Message-ID
<20160420162825.62380-2-gitter.spiros@gmail.com>
In-Reply-To
<20160420162825.62380-1-gitter.spiros@gmail.com>
Describe the purpose of the GIT_TRACE_CURL environment variable.
Helped-by: Torsten Bögershausen <tboegi@web.de>
Helped-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
Helped-by: Junio C Hamano <gitster@pobox.com>
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
---
 Documentation/git.txt | 8 ++++++++
 1 file changed, 8 insertions(+)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 8afe349..958db0f 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -1075,6 +1075,14 @@ of clones and fetches.
 	cloning of shallow repositories.
 	See 'GIT_TRACE' for available trace output options.
 
+'GIT_TRACE_CURL'::
+	Enables a curl full trace dump of all incoming and outgoing data,
+	including descriptive information, of the git transport protocol.
+	This is similar to doing curl --trace-ascii on the command line.
+	This option overrides setting the GIT_CURL_VERBOSE environment
+	variable.
+	See 'GIT_TRACE' for available trace output options.
+
 'GIT_LITERAL_PATHSPECS'::
 	Setting this variable to `1` will cause Git to treat all
 	pathspecs literally, rather than as glob patterns. For example,
-- 
2.8.1.383.g31b84cc
Previous: Elia PintoNext: Elia Pinto
Message 2 of 10 in “[PATCHv3 0/3] Implements the GIT_TRACE_CURL environment variable”
  1. Elia PintoApr 20, 2016
  2. 1/3 git.txt: document the new GIT_TRACE_CURL environment variableElia Pinto, Apr 20, 2016
  3. 2/3 imap-send.c: introduce the GIT_TRACE_CURL enviroment variableElia Pinto, Apr 20, 2016
  4. 3/3 http.c: implements the GIT_TRACE_CURL environment variableElia Pinto, Apr 20, 2016
  5. Junio C HamanoApr 20, 2016
  6. Ramsay JonesApr 20, 2016
  7. Junio C HamanoApr 20, 2016
  8. Junio C HamanoApr 20, 2016
  9. Ramsay JonesApr 20, 2016
  10. Jeff KingApr 20, 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.