Christian Couder writes:
> What scenario do you have in mind where people would have to do things
> differently?
They eventually will see a system in which that they do not have do
anything after flipping the configuration, yet will still see stale
"you must run 'git status'" on their websearche
On Thu, Dec 31, 2015 at 12:23 AM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> On Tue, Dec 29, 2015 at 11:35 PM, Junio C Hamano wrote:
>> ...
>>> While the above is not wrong per-se, from the point of those who
>>> looked for these options (that is, those who wanted to do a one-shot
>>>
Christian Couder writes:
> On Tue, Dec 29, 2015 at 11:35 PM, Junio C Hamano wrote:
> ...
>> While the above is not wrong per-se, from the point of those who
>> looked for these options (that is, those who wanted to do a one-shot
>> enabling or disabling of the feature, perhaps to try it out to s
On Tue, Dec 29, 2015 at 11:35 PM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> +core.untrackedCache::
>> + Determines if untracked cache will be automatically enabled or
>> + disabled. It can be `keep`, `true` or `false`. Before setting
>> + it to `true`, you should check tha
Christian Couder writes:
> +core.untrackedCache::
> + Determines if untracked cache will be automatically enabled or
> + disabled. It can be `keep`, `true` or `false`. Before setting
> + it to `true`, you should check that mtime is working properly
> + on your system.
> + See
When we know that mtime is fully supported by the environment, we
might want the untracked cache to be always used by default without
any mtime test or kernel version check being performed.
Also when we know that mtime is not supported by the environment,
for example because the repo is shared ove
6 matches
Mail list logo
