Re: sparse support in pu
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 17, 2009, 16:05 UTC
- Message-ID
- <7v7hx2xw6p.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <alpine.DEB.1.00.0908171522510.4991@intel-tinevez-2-302>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 7 quoted lines
>> That's funny. I have a git tree that would benefit from sparse checkout. >> I know which path I _don't_ want. Specifying all the paths I want would >> be a rather longer (and more error-prone) list. I suspect it would be >> best to support both. > > Yes, I agree, but the common case is for people to know what they are > working on, right?
I either may be working on Documentation/ (I know I do not care about everthing else so I can afford to list Makefile and Documentation/ in the "interesting" list), or I either may be working on code (I do not know how many code directories there are, and do not care to list them, but I know I do not need Documentation/ and contrib/). You need both ways.
And with .gitignore syntax you can have both.