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

From: Jeff King <peff@peff.net>
Date: Sep 20, 2013, 03:38 UTC
Message-ID: <20130920033821.GD15101@sigill.intra.peff.net>
In-Reply-To: <SDZYUVdaTCUzXD8wPVQvMjQwMzM4MTcx@IBMLT4>

On Fri, Sep 20, 2013 at 12:54:45PM +0930, Martin Gregory wrote:

Show 11 quoted lines

> >>  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.
> 
> Even if you only do it as part of a verbose option?
> 
> My thinking was that when you specify verbose, you are saying "I don't
> mind a bit of noise in order to find what I'mlooking for".

I don't mind a special option to turn this on for debugging, but the normal "-v" for read-tree is not "show me random noise", but rather "keep me occupied with a progress bar". If it were triggered by two or more "-v" options (which could also contain other debugging output), I'd be more sympathetic.

-Peff