Re: Expanding Includes in .gitignore

From: Aaron Pelly <aaron@pelly.co>
Date: Oct 28, 2016, 09:32 UTC
Message-ID: <cc23eece-d693-9e40-78fe-3bafe6bcad3a@pelly.co>
In-Reply-To: <xmqqwpgt2ng2.fsf@gitster.mtv.corp.google.com>

On 28/10/16 15:54, Junio C Hamano wrote:

Show 11 quoted lines

> Jeff King <peff@peff.net> writes:
> 
>> However, as I said elsewhere, I'm not convinced this feature is all that
>> helpful for in-repository .gitignore files, and I think it does
>> introduce compatibility complications. People with older git will not
>> respect your .gitignore.d files. Whereas $GIT_DIR/info is purely a local
>> matter.
> 
> As I do not see the point of making in-tree .gitignore to a forest
> of .gitignore.d/ at all, compatibility complications is not worth
> even thinking about, I would have to say.

Well; that saves some work. :)

I do not suggesting making this mandatory. I think it adds value and it is a common and understood mechanism. But, if it is abhorrent, consider:

There is precedent for including files in git-config. This could be extended to ignore files. The code is not similar, but the concept is. I could live with it.

Or how about a new githook that can intelligently create or return the details? This would be my least favourite option unless it was configured in an obvious place.

Finally, if this is a bad-idea, as I asked in the beginning, I will consider the equine expired, cease flagellation and apologise for the noise.