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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lidong Yan <yldhome2d2@xxxxxxxxx> writes:

> Bryan Lee <hi@xxxxxxxxxx> 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.





[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux