Re: [PATCH 2/2] give exclude mechanism a debug option

From: Jeff King <peff@peff.net>
Date: Feb 7, 2009, 11:44 UTC
Message-ID: <20090207114444.GB18079@coredump.intra.peff.net>
In-Reply-To: <7vljsizog1.fsf@gitster.siamese.dyndns.org>

On Fri, Feb 06, 2009 at 11:38:38PM -0800, Junio C Hamano wrote:

Show 10 quoted lines

> >   2. If you ask for "foo/bar", and "foo/" is ignored, the
> >      output will show only "foo: exclude: foo". This is an
> >      artifact of the calling interface: you don't ask "is
> >      foo/bar excluded", but rather while recursing through
> >      "foo/" you ask "should I bother even recursing into
> >      foo?". So the exclusion code never even knows that you
> >      might have cared about foo/bar in the first place.
> 
> I do not see why it is a problem.  It exactly is what you want to know,
> isn't it?

Because I would expect "git check-ignore foo/bar | grep ^foo/bar:" to tell me if and how foo/bar is being excluded. But I have to instead check for ^foo and ^foo/bar.

Not a big deal, perhaps. But it just seems like counter-intuitive output for a query about how a specific path is excluded.

-Peff