Re: Expanding Includes in .gitignore

From: Jacob Keller <jacob.keller@gmail.com>
Date: Oct 27, 2016, 21:39 UTC
Message-ID: <CA+P7+xrEz7XhZ4fHYUA7gjJtbW8WUEWQhtpAQ+zMC9nVE135iw@mail.gmail.com>
In-Reply-To: <20161027210458.ptzh4y75dkfaixeo@sigill.intra.peff.net>

On Thu, Oct 27, 2016 at 2:04 PM, Jeff King <peff@peff.net> wrote:

Show 6 quoted lines

> I'm not convinced this is needed for in-repo .gitignore files. The point
> is that you are pulling together separate files that may be administered
> independently. But git repositories inherently have a whole-project
> view. I'm not sure that separate files buy you a lot there. And the
> compatibility issues are more complicated.
>

I had just assumed it would be used everywhere, so I hadn't really considered whether that was any reason not to. I personally like the idea of splitting my git ignores into separate files just so each file can be about one thing, but I guess it's not really a problem either way.

Show 9 quoted lines

> I do agree that:
>
>   cd .git/info
>   git clone /my/exclude/repo exclude ;# or exclude.d
>
> should work; ignoring dotfiles when reading the directory solves that,
> and is a pretty standard solution.
>
> -Peff