I had a couple comments and questions about the sparse stuff recently merged into pu. First, I think it's an awesome feature. It's a nice solution to my problems (1.5 GB tree where most people only need a small subset, but with a lot of shared pieces). 1. Have people decided whether it should be on by default if you have a .git/info/sparse file? I'd definitely like it to be on by default. When I first tried it, I didn't realize I had to use --sparse to git checkout to get it to use the sparse rules. The same goes for a merge I did that happened to have a file in the excluded area (it included it because I didn't use --sparse to git merge). 2. Is it not hooked up to git reset yet? I did a git checkout --sparse and things look liked I expected then I did a git reset --hard origin/master and it started checking out all the stuff previously excluded via .git/info/sparse. I tried --sparse, but it didn't know about that option. 3. One thing that was confusing is that I needed a trailing slash on directories in .git/info/sparse to get them excluded. This seems different than .gitignore, which works for me without the trailing slash. BTW...How to people normally try out stuff in pu? Do you just replace your normal git stuff with the pu build? That's what I did because I wasn't sure if I did /test/git if the other tools git invokes would use the release version of git or the ones relative to itself (i.e. the ones in /test/ for me). It seems like the only way to really test stuff is to use it for your real work, but I also don't want to corrupt our production repositories by using an experimental version of git. -- 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