Re: [PATCH v2] run-command.c: print env vars when GIT_TRACE is set

From: Duy Nguyen <pclouds@gmail.com>
Date: Jan 12, 2018, 09:23 UTC
Message-ID: <CACsJy8BrLJiwoKugJQhFj-TvUBDG5tcdTeOGnYPZ=H=6kSHdzA@mail.gmail.com>
In-Reply-To: <xmqq4lnsyz4l.fsf@gitster.mtv.corp.google.com>

On Fri, Jan 12, 2018 at 2:27 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 5 quoted lines

> I wonder how common it would be to attempt exporting a variable with
> the same value, and to attempt unsetting a variable that is not
> exported, which might help you reduce the clutter by hiding stuff
> that truly do not matter, while keeping what matters (possibly
> including the "unset" part).

It looks pretty good actually. This is with 'git status' and a repo with submodule 'foo'.

trace: run_command: cd 'foo'; unset GIT_PREFIX; git 'status' '--porcelain=2'

Thanks for the suggestion.

-- 
Duy

$ 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.