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

[PATCH] run_command(): respect GIT_TRACE

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jul 7, 2008, 13:41 UTC
Message-ID
<alpine.DEB.1.00.0807071441190.18205@racer>

When GIT_TRACE is set, the user is most likely wanting to see an external command that is about to be executed.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
 run-command.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/run-command.c b/run-command.c
index 2ce8c2b..6e29fdf 100644
--- a/run-command.c
+++ b/run-command.c
@@ -65,6 +65,8 @@ int start_command(struct child_process *cmd)
 		cmd->err = fderr[0];
 	}
 
+	trace_argv_printf(cmd->argv, "trace: run_command:");
+
 #ifndef __MINGW32__
 	cmd->pid = fork();
 	if (!cmd->pid) {
-- 
1.5.6.2.402.g95b5ab.dirty
Next: Junio C Hamano
Message 1 of 2 in “run_command(): respect GIT_TRACE”
  1. run_command(): respect GIT_TRACEJohannes Schindelin, Jul 7, 2008
  2. Junio C HamanoJul 7, 2008

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.