From: Christian Couder <christian.couder@gmail.com>
Date: Thu, 24 Dec 2015 21:10:29 GMT
Subject: Re: [PATCH v3 10/11] config: add core.untrackedCache
Message-ID: <CAP8UFD0penKjBBUW-9aPJ=T8x7WfhZGDtH1-jBsuJ4CTb2mrXw@mail.gmail.com>
In-Reply-To: <CACsJy8C0CwbFy+Ghk3EWTyhqPYcr6xE5jczumWW98cAAHdfmPg@mail.gmail.com>

On Thu, Dec 24, 2015 at 11:13 AM, Duy Nguyen <pclouds@gmail.com> wrote:
> On Thu, Dec 24, 2015 at 4:03 AM, Christian Couder
> <christian.couder@gmail.com> wrote:
>>  --force-untracked-cache::
>> -       For safety, `--untracked-cache` performs tests on the working
>> -       directory to make sure untracked cache can be used. These
>> -       tests can take a few seconds. `--force-untracked-cache` can be
>> -       used to skip the tests.
>> +       Same as `--untracked-cache`. Provided for backwards
>> +       compatibility with older versions of Git where
>> +       `--untracked-cache` used to imply `--test-untracked-cache` but
>> +       this option would enable the extension unconditionally.
>
> Nit. The reason --force-untracked-cache remains can probably stay in
> the commit message. Here we can simply say "synonym of
> --untracked-cache, deprecated" or something like that (or even ".. to
> be deleted in version N.M").

Yeah, I think "deprecated" should be enough and clearer, but I will
see with AEvar who helped me on this.

Thanks,
Christian.