Re: is there a truly compelling rationale for .git/info/exclude?

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Oct 6, 2017, 19:23 UTC
Message-ID: <20171006192359.GW19555@aiede.mtv.corp.google.com>
In-Reply-To: <alpine.LFD.2.21.1710061337300.14079@localhost.localdomain>

Hi,

Robert P. J. Day wrote:

> On Fri, 6 Oct 2017, Junio C Hamano wrote:

Show 8 quoted lines

>> Don't waste time by seeking a "compelling" reason.  A mere "this is
>> the most expedite way to gain convenience" back when something was
>> introduced could be an answer, and it is way too late to complain
>> about such a choice anyway.
>
>   perfectly respectable answer ... it tells me that, between
> .gitignore files and core.excludesFile, there's not much left for
> .git/info/exclude to do, except in weird circumstances.

I use .git/info/exclude in what I don't consider to be weird circumstances.

But I am not motivated to say more than that without knowing what my answer is going to be used for. E.g. is there a part of the gitignore(5) man page where such an explanation would make it less confusing and more useful?

Thanks, Jonathan