Hi, On Mon, 17 Aug 2009, Junio C Hamano wrote: > I'd say that assume-unchanged is a promise you make git that you won't > change these paths, and in return to the promise git will give you > faster response by not running lstat on them. Having changes in such > paths is your problem and you deserve these chanegs to be lost. At > least, that is the interpretation according to the original > assume-unchanged semantics. That's why I did not suggest using assume-unchanged (which the guy did previously, and was burnt, deservedly, as you say). However, my illustration of the scenario was only to one end, namely to convince all of you that assume-changed != sparse. And maybe to the end to explain that sparse checkout could help this guy. Ciao, Dscho -- 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