Re: [RFC PATCH v3 8/8] --sparse for porcelains
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Aug 13, 2009, 07:20 UTC
- Message-ID
- <fcaeb9bf0908130020meaed129j5d6a4f04a6878bd0@mail.gmail.com>
- In-Reply-To
- <7v3a7xa6e5.fsf@alter.siamese.dyndns.org>
2009/8/12 Junio C Hamano <gitster@pobox.com>:
Show 6 quoted lines
> It could also require core.sparseworktree configuration set to true if we > are really paranoid, but without the actual sparse specification file > flipping that configuration to true would not be useful anyway, so in > practice, giving --sparse-work-tree option to these Porcelain commands > would be no-op, but --no-sparse-work-tree option would be useful to > ignore $GIT_DIR/info/sparse and populate the work tree fully.
Only part "ignore $GIT_DIR/info/sparse" is correct. "--no-sparse-work-tree" would not clear CE_VALID from all entries in index (which is good, if you are using CE_VALID for another purpose).
To quit sparse checkout, you must create an empty $GIT_DIR/info/sparse, then do "git checkout" or "git read-tree -m -u HEAD" so that the tree is full populated, then you can remove $GIT_DIR/info/sparse. Quite unintuitive..
-- Duy