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

[PATCH] Documentation/git.txt: clarify that GIT_TRACE=/path appends

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Sep 4, 2018, 00:05 UTC
Message-ID
<20180904000544.13907-1-szeder.dev@gmail.com>

The current wording of the description of GIT_TRACE=/path/to/file ("... will try to write the trace messages into it") might be misunderstood as "overwriting"; at least I interpreted it that way on a cursory first read.

State it more explicitly that the trace messages are appended.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
---
 Documentation/git.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git.txt b/Documentation/git.txt
index dba7f0c18e..74a9d7edb4 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -599,8 +599,8 @@ trace messages into this file descriptor.
 +
 Alternatively, if the variable is set to an absolute path
 (starting with a '/' character), Git will interpret this
-as a file path and will try to write the trace messages
-into it.
+as a file path and will try to append the trace messages
+to it.
 +
 Unsetting the variable, or setting it to empty, "0" or
 "false" (case insensitive) disables trace messages.
-- 
2.19.0.rc0.188.g56c5ee2db1
Message 1 of 1 in “Documentation/git.txt: clarify that GIT_TRACE=/path appends”
  1. Documentation/git.txt: clarify that GIT_TRACE=/path appendsSZEDER Gábor, Sep 4, 2018

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.