On Mon, Aug 17, 2009 at 9:23 AM, Johannes Schindelin wrote: > On Mon, 17 Aug 2009, Peter Harris wrote: >> On Mon, Aug 17, 2009 at 8:29 AM, Johannes Schindelin wrote: >> > If I want to have a sparse checkout, I know which files I _want_. >> >> 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 would presume so, but anecdotal "evidence" points the other way. I don't have a statistically significant number of samples. Maybe it should have been asked in the Git User's Survey? ;-) >> Does sparse use the same parser as .gitignore? (I guess not, if it >> handles trailing slashes differently?) If so, it would be trivial to >> turn "exclude path" into "exclude all but path" (or vice-versa) with: >> >> * >> !path > > That was the idea behind my suggestion to allow .gitignore syntax. And > indeed, that is what happened. Excellent. In that case, I don't care which way around the default is. Thanks, Peter Harris -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html