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

Re: [PATCH] perf: do allow `GIT_PERF_*` to be overridden again

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 22, 2025, 15:37 UTC
Message-ID
<xmqqzfg8438h.fsf@gitster.g>
In-Reply-To
<20250422104125.GA1460472@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 21 quoted lines
> The original patch in this thread did something like:
>
>   git_perf_settings=$(...pull GIT_PERF_* from env...)
>    . ../test-lib.sh
>   eval "$git_perf_settings"
>
> That is, we stash away the environment, then load test-lib.sh, which
> overwrites the environment, and then we restore (some of) the original
> values.
>
> In that merge, the test-lib.sh inclusion is moved (and in fact is now
> accompanied by an explicit inclusion of GIT-BUILD-OPTIONS), and we now
> have:
>
>    . "$GIT_BUILD_DIR"/GIT-BUILD-OPTIONS
>    . "$GIT_SOURCE_DIR"/t/test-lib.sh
>    git_perf_settings=$(...)
>    eval "$git_perf_settings"
>
> Which of course does nothing. We need to set $git_perf_settings before
> those other source lines (and the eval must remain after them).
Right.  Thanks.
Previous: Jeff King
Message 6 of 6 in “perf: do allow `GIT_PERF_*` to be overridden again”
  1. perf: do allow `GIT_PERF_*` to be overridden againJohannes Schindelin via GitGitGadget, Apr 4, 2025
  2. Derrick StoleeApr 4, 2025
  3. Jeff KingApr 19, 2025
  4. Junio C HamanoApr 20, 2025
  5. Jeff KingApr 22, 2025
  6. Junio C HamanoApr 22, 2025

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.