Re: [PATCH v1 05/19] update-index: warn in case of split-index incoherency
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Nov 1, 2016, 23:00 UTC
- Message-ID
- <CAP8UFD18gcMJY7zjXw+ry6Kq2Foug9r0e=OVgZ_hcFkEVfnChA@mail.gmail.com>
- In-Reply-To
- <xmqqlgx3owbg.fsf@gitster.mtv.corp.google.com>
On Tue, Nov 1, 2016 at 8:05 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 24 quoted lines
> Duy Nguyen <pclouds@gmail.com> writes:
>
>>> diff --git a/builtin/update-index.c b/builtin/update-index.c
>>> index b75ea03..a14dbf2 100644
>>> --- a/builtin/update-index.c
>>> +++ b/builtin/update-index.c
>>> @@ -1098,12 +1098,21 @@ int cmd_update_index(int argc, const char **argv, const char *prefix)
>>> }
>>>
>>> if (split_index > 0) {
>>> + if (git_config_get_split_index() == 0)
>>> + warning("core.splitIndex is set to false; "
>>> + "remove or change it, if you really want to "
>>> + "enable split index");
>>
>> Wrap this string and the one below with _() so they can be translated.
>
> True.
>
> I further wonder if a natural reaction from users after seeing this
> message is "I do want to--what else would I use that option to run
> you for? Just do as you are told, instead of telling me what to
> do!". Is this warning really a good idea, or shouldn't these places
> be setting the configuration?In 435ec090ec (config: add core.untrackedCache, 2016-01-27) we decided to just use warning() after discussing if we should instead set the configuration.