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

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 12, 2017, 23:18 UTC
Message-ID: <alpine.DEB.2.21.1.1710130116430.40514@virtualbox>
In-Reply-To: <alpine.LFD.2.21.1710061337300.14079@localhost.localdomain>

Hi Robert,

[who I had to cull from the To:/Cc: headers, as my mailer consistently told me that there is no valid DNS record to route mail to rpjday@crashcourse.ca, which *is* weird.]

On Fri, 6 Oct 2017, Robert P. J. Day wrote:

Show 10 quoted lines

> On Fri, 6 Oct 2017, Junio C Hamano wrote:
> 
> > 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 to keep worktrees in subdirectories of the "main" worktree.

That's not really weird. It's just something few people do, but that's not the same as "weird".

Ciao, Johannes