Re: What's cooking in git.git (Nov 2008, #06; Wed, 26)

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Dec 7, 2008, 12:27 UTC
Message-ID: <fcaeb9bf0812070427s64438216s41bf1294aa6398a3@mail.gmail.com>
In-Reply-To: <alpine.LNX.1.00.0812061238260.19665@iabervon.org>

On 12/7/08, Daniel Barkalow <barkalow@iabervon.org> wrote:

Show 8 quoted lines

>  > There is not much work for CE_NO_CHECKOUT on plumbling level except
>  > some fixes. The last half of the series, for porcelain level, you will
>  > see more.
>
>
> For the porcelain level, do we need the difference to be in the index? If
>  the porcelain knows the sparse checkout area and can instruct the plumbing
>  appropriately, the information shouldn't need to be stored in the index

This was discussed since the beginning of this feature. I recall that the index reflects worktree, and because we mark CE_NO_CHECKOUT on file basis, it's best to save the information there, not separately. We do save high level information to form the checkout area (sparse patterns) in the last half, but basically you should be able to live without that.

Show 5 quoted lines

>  unless it's ever important to remember whether an entry is CE_VALID due to
>  having been outside the checkout when the index was written, even though
>  the checkout area now includes it. I don't have a good intuition as to
>  what ought to happen if the user manually changes what's specified for
>  checkout without actually updating the index and working tree.

So if a user changes worktree without updating index, they will have the same results as they do now: files are shown as modified if they don't have CE_NO_CHECKOUT set. If those files do, they are considered 'orphaned' or staled and are recommended to be removed/updated to avoid unexpected consequences (not availble this this first half series because that belongs to "git status").

-- 
Duy