Re: Expanding Includes in .gitignore

From: Aaron Pelly <aaron@pelly.co>
Date: Oct 27, 2016, 22:30 UTC
Message-ID: <ad01f925-dcfd-4b98-6998-73965c72f69f@pelly.co>
In-Reply-To: <20161027210753.btc7zbndhdocsbwa@sigill.intra.peff.net>

On 28/10/16 10:07, Jeff King wrote:

> 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.

I know. I don't think it's a serious compatibility issue, but more important people may disagree, in which case I'll have to review my stance. I think the pros of it working everywhere outweigh the cons.

I will say that I am a proponent of consistency and obviousness. I would rather this worked the same everywhere or it was a completely novel component in $GIT_DIR.

I don't think I like the idea much, but it would be possible to magically generate an ignore file from a directory.

> But perhaps there is a use case I'm missing.

A new repo where the dev tools haven't been standardised yet. New tool, new file. Simple, and somewhat self documenting as a table of contents in .gitignore.d