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

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Dec 12, 2008, 16:08 UTC
Message-ID: <fcaeb9bf0812120808y656c0c6bx9d1c44ea00aeb7b9@mail.gmail.com>
In-Reply-To: <alpine.LNX.1.00.0812111520490.19665@iabervon.org>

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

Show 11 quoted lines

>  > Well, if you set core.defaultsparse properly, those files should
>  > appear/disappear as you wish (and as of now if you define your
>  > checkout area with "git checkout --{include-,exclude-,}sparse" then
>  > core.defaultsparse should be updated accordingly). I don't say
>  > core.defaultsparse is perfect.
>
>
> Right, so in order to get reasonable behavior, the user must use
>  --{include,exclude}-sparse. I think that this should be the *default*
>  behavior, and probably the *only porcelain-supported* behavior, because
>  otherwise it's confusing.

It's pretty hard (or intrusive) to enforce such behaviour. How about showing files that does not match core.defaultsparse in "git status" along with instructions how to add them to core.defaultsparse? That way people can keep it consistent and less modification to current code.

-- 
Duy