2009/8/11 Nguyễn Thái Ngọc Duy <pclouds@xxxxxxxxx>: > [1] .git/info/sparse has the same syntax as .git/info/exclude. Files > that match the patterns will be set as CE_VALID. Does this mean it will only support excluding paths you don't want rather than letting you only include paths you do want? I'm currently using your other patch series that lets you include or exclude paths (via config variable) and I find that I mostly use the include side of it with only a few excluded paths. This is because I typically want to include only a small subset of the repository so using excludes would require a pretty large list and any time somebody adds new files, I'd have to update the exclude list. I appreciate the flexibility of the script to control what is included or excluded, but like some other comments here, I like the simplicity of having built-in support for including/excluding paths without having to write a script to do it. Some of my projects run on Windows so scripting is more difficult there. -- 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