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

[PATCH 1/1] trace2: Add variable description to git.txt

From
Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Date
May 10, 2019, 19:44 UTC
Message-ID
<768bdf1c210fd34776f667b080a23eb6f9e17125.1557517464.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.189.git.gitgitgadget@gmail.com>
From: Derrick Stolee <dstolee@microsoft.com>

Documentation/technical/api-trace2.txt contains the full details of the trace2 API and the GIT_TR2* environment variables. However, most environment variables are included in Documentation/git.txt, including the GIT_TRACE* variables.

Add a brief description of the GIT_TR2* variables with links to the full technical details. The biggest difference from the original variables is that we can specify a Unix Domain Socket. Mention this difference, but leave the details to the technical documents.

Reported-by: Szeder Gábor <szeder.dev@gmail.com>
Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
---
 Documentation/git.txt | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 00156d64aa..e802886999 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -661,6 +661,27 @@ of clones and fetches.
 	When a curl trace is enabled (see `GIT_TRACE_CURL` above), do not dump
 	data (that is, only dump info lines and headers).
 
+`GIT_TR2`::
+	Enables more detailed trace messages from the "trace2" library.
+	Output from `GIT_TR2` is a simple text-based format for human
+	readability.
++
+The `GIT_TR2` variables can take many values. Any value available to
+the `GIT_TRACE` variables is also available to `GIT_TR2`. The `GIT_TR2`
+variables can also specify a Unix Domain Socket. See
+link:technical/api-trace2.html[Trace2 documentation] for full details.
+
+`GIT_TR2_EVENT`::
+	This setting writes a JSON-based format that is suited for machine
+	interpretation. See link:technical/api-trace2.html[Trace2 documentation]
+	for full details.
+
+`GIT_TR2_PERF`::
+	In addition to the text-based messages available in `GIT_TR2`, this
+	setting writes a column-based format for understanding nesting
+	regions. See link:technical/api-trace2.html[Trace2 documentation]
+	for full details.
+
 `GIT_REDACT_COOKIES`::
 	This can be set to a comma-separated list of strings. When a curl trace
 	is enabled (see `GIT_TRACE_CURL` above), whenever a "Cookies:" header
-- 
gitgitgadget
Previous: Derrick Stolee via GitGitGadgetNext: SZEDER Gábor
Message 2 of 13 in “trace2: Add variable description to git.txt”
  1. 0/1 trace2: Add variable description to git.txtDerrick Stolee via GitGitGadget, May 10, 2019
  2. 1/1 trace2: Add variable description to git.txtDerrick Stolee via GitGitGadget, May 10, 2019
  3. SZEDER GáborMay 10, 2019
  4. 1/2 trace2: rename environment variables to GIT_TRACE2*SZEDER Gábor, May 19, 2019
  5. 2/2 trace2: document the supported values of GIT_TRACE2* env variablesSZEDER Gábor, May 19, 2019
  6. Junio C HamanoMay 28, 2019
  7. Derrick StoleeMay 28, 2019
  8. Jeff HostetlerMay 29, 2019
  9. Ævar Arnfjörð BjarmasonMay 28, 2019
  10. Jeff HostetlerMay 29, 2019
  11. Junio C HamanoMay 29, 2019
  12. Revert "test-lib: whitelist GIT_TR2_* in the environment"Ævar Arnfjörð Bjarmason, Jun 12, 2019
  13. Junio C HamanoJun 12, 2019

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.