Re: sparse checkout file with windows line endings doesn't work

From: Jeff King <peff@peff.net>
Date: Sep 20, 2013, 03:17 UTC
Message-ID: <20130920031705.GA15101@sigill.intra.peff.net>
In-Reply-To: <SDZYTDk4NyMxKC4hPVQvMjM1MDUxNjg3@IBMLT4>

On Fri, Sep 20, 2013 at 11:22:01AM +0930, Martin Gregory wrote:

Show 10 quoted lines

> When something goes wrong, there appears to be no way to understand what
> git thinks it's reading.   I'm not sure if such a way, if it existed, would help with
> trailing spaces, but if you could say
> 
> git read-tree -muv HEAD
> 
> and it would say
> 
> reading '.git\info\sparse-checkout'...
> rule '/CONFIGURATION ' - no matches

I don't think you can do that in the general case of read-tree. You may have sparse paths that exist in some commits, but not others. As you move around in history, a sparse entry that does not match might do so because it is poorly written, or it might do so because you just don't happen to have any matching paths in the commit you are moving to. The former is a problem, but warning on the latter would be useless noise.

-Peff