Re: sparse support in pu

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: Aug 17, 2009, 12:53 UTC
Message-ID: <fcaeb9bf0908170553k7008d7a0u1f5955f227a991df@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0908171425410.4991@intel-tinevez-2-302>

On Mon, Aug 17, 2009 at 7:29 PM, Johannes Schindelin<Johannes.Schindelin@gmx.de> wrote:

Show 22 quoted lines

> Hi,
>
> On Mon, 17 Aug 2009, Nguyen Thai Ngoc Duy wrote:
>
>> On Mon, Aug 17, 2009 at 5:36 PM, Johannes Sixt<j.sixt@viscovery.net> wrote:
>>
>> > In order to advocate my earlier proposal: Name the file
>> > .git/info/phantoms, then it's clear: "The files mentioned here are
>> > phantoms" - they exist in the index, but not in the worktree; no
>> > phantoms means that everything is checked out.
>>
>> OK. Phantom checkout, must be unique in VCS world ;-) If no one objects
>> my next series will use this name as it's better than "sparse" and
>> "assume-unchanged" is just too vague. Would option names to
>> enable/disable this be --with[out]-phantoms?
>
> The term 'phantom' is not specified at all.  At least interested people on
> the mailing list know 'sparse'.  But I agree that the naming is a major
> problem, hence my earlier (unanswered) call.
>
> However, I would find specifying what you do _not_ want in that file
> rather unintuitive, in the same leage as receive.denyNonFastForwards = no.

But .gitignore is because I do _not_ want some files. Hey, how about worktree-ignore? Turning it to positive matching instead of excluding is not hard, but I have a feeling that people (OK, I) usually want to ignore some directories. Applying trick:

* !foo/ !bar/

to have foo and bar ignored too often would not be fun.

-- 
Duy