From: Nguyen Thai Ngoc Duy Date: Wed, 21 Sep 2011 09:26:04 GMT Subject: Re: [PATCH 3/3] git-read-tree.txt: correct sparse-checkout and skip-worktree description Message-ID: In-Reply-To: <31152a2ddb83e37be1efce1d0cd742b71ea3efdd.1316590874.git.git@drmicha.warpmail.net> On Wed, Sep 21, 2011 at 5:48 PM, Michael J Gruber wrote: > The description of .git/info/sparse-checkout and > skip-worktree is exactly the opposite of what is true, which is: > > If a file matches a pattern in sparse-checkout, then (it is to be > checked out and therefore) skip-worktree is unset for that file; > otherwise, it is set (so that it is not checked out). > > Currently, the opposite is documented, and (consistently) read-tree's > behavior with respect to bit flips is descibed incorrectly. > > Fix it. Ack. > In hindsight, it would have been much better to have a "sparse-ignore" > or "sparse-skip" file so that an empty file would mean a full checkout, > and the file logic would be analogous to that of .gitignore, excludes > and skip-worktree. .gitignore works towards excluding files. No rule means no excluding. sparse-checkout file works towards including files, no rule means no inclusion. -- Duy