From: Nguyen Thai Ngoc Duy Date: Mon, 17 Aug 2009 11:41:29 GMT Subject: Re: sparse support in pu Message-ID: In-Reply-To: <4A8932BB.7030002@viscovery.net> On Mon, Aug 17, 2009 at 5:36 PM, Johannes Sixt wrote: > Nguyen Thai Ngoc Duy schrieb: >> [I haven't read the rest of the mail, will read it through later] >> >> On Mon, Aug 17, 2009 at 3:49 PM, wrote: >>> It would be nice if .git/info/sparse is there by default (like >>> .git/info/exclude) with some commented out instructions (also like >>> .git/info/exclude). >> >> No it can't be there by default. An empty .git/info/sparse means clear >> assume-unchanged bit out of all files in index. It's not the same as >> lacking .git/info/sparse (which does disable sparse checkout feature). > > Huh? Shouldn't the meaning of .git/info/sparse be: "the files mentioned in > this file are not checked out." That is, if the file is empty, then no > file is not checked out, IOW, all files are checked out. That's correct. Empty .git/info/sparse -> no assume-unchanged files -> all files are checked out. That's what I meant. It's different from empty .git/info/sparse as "don't touch index and worktree, leave them as they are no matther if they have assume-unchanged files". > 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? -- Duy