Re: [BUG] git pull ignores pull.autostash=true configuration when used with --git-dir and --work-tree flags on a bare repository

From: Johannes Sixt <j6t@kdbg.org>
Date: Jul 16, 2025, 05:55 UTC
Message-ID: <26cef1b9-1f17-447e-b647-3d32a3984997@kdbg.org>
In-Reply-To: <6AEC3113-D687-42E0-B6D0-DF62FA1A9A8B@gmail.com>

Am 16.07.25 um 03:39 schrieb Lidong Yan:

Show 5 quoted lines

> Junio C Hamano <gitster@pobox.com> writes:
>> Lidong Yan <yldhome2d2@gmail.com> writes:
>>> Bryan Lee <hi@looping.me> wrote:
>>>> 2. Or at least document common misconceptions like `pull.autostash` in
>>>> the git-config man page?

Show 6 quoted lines

>> There always are end-user or third-party defined keys that are not
>> known to us, and we cannot tell if an unknown variable is such a
>> end-user defined one or a typo of a known one.
> 
> For every git_xxx_config(), we could add a register function like
> git_xxx_config_register(), which looks like:

Instead of this complexity, it is most likely a lot easier to fix the origin of the misconception that `pull.autostash` is the correct configuration. After all, it isn't even mentioned in the git-config nor the git-pull man page.

-- Hannes