Re: ls-files --exclude broken?

From: Jay Soffian <jaysoffian@gmail.com>
Date: Sep 16, 2010, 00:33 UTC
Message-ID: <AANLkTikd5uZFk8-d7wmB8ZEqOy5=RWsDNnrsHqAQZhkz@mail.gmail.com>
In-Reply-To: <20100916001636.GA2371@sigill.intra.peff.net>

On Wed, Sep 15, 2010 at 8:16 PM, Jeff King <peff@peff.net> wrote:

> It's not just the command line. It's also what's in .gitignore files. If
> you disable just half of that, then you get the awful behavior that some
> excludes apply to index files, and some don't.

Files matched by the standard excludes are not likely to be in the index in the first place. So in that sense, arguably -x is special.

But nonetheless, I agree with you, and since the user must specifically ask ls-files for the various exclusions, I think it makes sense to apply those even to cached files.

> It would help if I understood exactly what you're trying to accomplish.

I'm building a project file for my editor and I want to exclude certain files that make no sense for it to care about even though they are part of the repo. So I tried:

$ git ls-files -x png -x jpg ...

and was confused by that not working. I've worked around this by just filtering the ls-files output through grep, but, ick.

j.