On Mon, Aug 17, 2009 at 3:02 PM, Johannes Schindelin<Johannes.Schindelin@xxxxxx> wrote: > And here comes the problem: if something is treated untracked because it > was outside of the sparse checkout, then I want it to be treated as > untracked _even if_ I happened to broaden the checkout by editing > .git/info/sparse. The file did not just magically become subject to > overwriting just because I edited .git/info/sparse (which could be a > simple mistake). Maybe I'm misunderstanding what you're saying, but why would you want a file that's become part of the checkout by editing .git/info/sparse to still be treated as untracked? If I have a file on that's excluded via .git/info/sparse then I edit .git/info/sparse to include it and switch to a branch that doesn't have that file, I'd expect that file to be deleted from the working copy if the content matches what's in the repository. If it's modified then I'd expect the branch switch to fail (like it would without a sparse checkout). -- 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