Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: >> 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. -- 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