Hi, On Mon, 17 Aug 2009, Nguyen Thai Ngoc Duy wrote: > On Mon, Aug 17, 2009 at 5:36 PM, Johannes Sixt<j.sixt@xxxxxxxxxxxxx> wrote: > > > In order to advocate my earlier proposal: Name the file > > .git/info/phantoms, then it's clear: "The files mentioned here are > > phantoms" - they exist in the index, but not in the worktree; no > > phantoms means that everything is checked out. > > OK. Phantom checkout, must be unique in VCS world ;-) If no one objects > my next series will use this name as it's better than "sparse" and > "assume-unchanged" is just too vague. Would option names to > enable/disable this be --with[out]-phantoms? The term 'phantom' is not specified at all. At least interested people on the mailing list know 'sparse'. But I agree that the naming is a major problem, hence my earlier (unanswered) call. However, I would find specifying what you do _not_ want in that file rather unintuitive, in the same leage as receive.denyNonFastForwards = no. If I want to have a sparse checkout, I know which files I _want_. 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