Re: [RFC PATCH 0/9] Narrow/Sparse checkout round 3: "easy mode"

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 16, 2008, 10:31 UTC
Message-ID: <7v1w0pdze0.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20080815142439.GA10609@laptop>

Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes:

> The implementation with insights from Junio turns out smaller and better
> (and I was thinking about applying it for huge maildir).

I think I can agree with the general direction this is taking, except that we would need to think about the transition plans. Note that I haven't really read through the full series yet.

> Another difference from the last round is "narrow rules" will not be preserved
> when switching branches. When you switch branch with no option, you will get
> full checkout. You may want to use --path|--add-path|--remove-path when
> switching branches to have narrow checkout again.

You could save the "narrow rules" in the extension section of the index. If the final form of this series needs to use a separate CE_NO_CHECKOUT bit (which would make the resulting index incompatible with the current git), the narrow rules section can be marked as "your git must understand this" class of extension to make sure that people do not mistakenly access an index written by this new version of git with the current or older git.

> Now back to technical POV. I did not reuse CE_VALID (assume unchanged) bit
> because it has been used for core.ignorestat.

I am not sure what's the relation between these two.