Re: [BUG] git pull ignores pull.autostash=true configuration when used with --git-dir and --work-tree flags on a bare repository
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 15, 2025, 20:46 UTC
- Message-ID
- <xmqqa555gp1i.fsf@gitster.g>
- In-Reply-To
- <1AD9A170-8E17-411D-A13B-EA7780CF4D39@gmail.com>
Lidong Yan <yldhome2d2@gmail.com> writes:
Show 9 quoted lines
> Bryan Lee <hi@looping.me> wrote: >> >> Would it be worthwhile to: >> 1. Add a warning when users set non-existent configuration keys? >> 2. Or at least document common misconceptions like `pull.autostash` in >> the git-config man page? > > I think adding a subcommand like ‘git config verify’ might be a way to > solve this problem.
Yes, but I do not know if it is feasible.
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.