On 01.12.15 21:31, Christian Couder wrote: > Most features in Git can be enabled or disabled using a simple > bool config variable and it would be nice if untracked cache > behaved the same way. > > This makes --[no-|force-]untracked-cache change the value of > core.untrackedCache in the repo config file, to avoid making > those options useless and because this avoids the untracked > cache being disabled by a kernel change or a directory > change. Of course this breaks some backward compatibility, > but the simplification and increased useability is worth it. Some loose thinking, how the core.untrackedcache and the command line can work together: core.untrackedcache = unset everything is as today if --test-untracked-cache is used on command line, the test is run, additionally the result is stored in the config variable core.untrackedcache core.untrackedcache = true same as --force-untracked-cache if --no-untracked-cache is given on command line, this has higher priority core.untrackedcache = false same as --no-untracked-cache if --force-untracked-cache is given on command line, this has higher priority Does this support the workflow described by Ævar ? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html