From: Junio C Hamano <gitster@pobox.com>
To: "Ebele Lynda Okolo via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>,
Usman Akinyemi <usmanakinyemi202@gmail.com>,
Ebele Lynda Okolo <okolo.ebelelynda@gmail.com>
Subject: Re: [PATCH] environment: move diff_auto_refresh_index into repo_config_values
Date: Mon, 02 Nov 2026 22:21:14 -0800 [thread overview]
Message-ID: <xmqqtslybfl1.fsf@gitster.g> (raw)
In-Reply-To: <pull.2289.git.1793607304156.gitgitgadget@gmail.com> (Ebele Lynda Okolo via GitGitGadget's message of "Mon, 02 Nov 2026 08:15:04 +0000")
"Ebele Lynda Okolo via GitGitGadget" <gitgitgadget@gmail.com>
writes:
> From: Lynndabel <okolo.ebelelynda@gmail.com>
>
> The diff_auto_refresh_index variable is currently a global,
> which makes it difficult to use Git as a library since
> global state can't be isolated between different repository
> instances.
We do not want to put it in repo_config_value, because access to the
structure will barf when given anything other than the_repository,
hence such a move does not help the "library" scene very much to
begin with.
It is only set in diff.c when the ui related configuration variable
is read from the git_config() callback. The callback is *not*
repository specific but is a synthesized computation result after
reading system, global, and repository configuration files, which is
another reason why it does not look like a good idea to tie this
setting to repo_config_values.
Thanks.
prev parent reply other threads:[~2026-11-03 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 8:15 [PATCH] environment: move diff_auto_refresh_index into repo_config_values Ebele Lynda Okolo via GitGitGadget
2026-11-03 6:21 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtslybfl1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=okolo.ebelelynda@gmail.com \
--cc=ps@pks.im \
--cc=usmanakinyemi202@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox