Re: [PATCH v3 1/6] worktree: new repo extension to manage worktree behaviors

From: Duy Nguyen <pclouds@gmail.com>
Date: Feb 1, 2016, 05:23 UTC
Message-ID: <CACsJy8DGsDFnX57eQ7rN2hkOR3Wuw_eQ9ED4e-9FhAm30sBFEQ@mail.gmail.com>
In-Reply-To: <jwvfuxd17bz.fsf-monnier+gmane.comp.version-control.git@gnu.org>

On Mon, Feb 1, 2016 at 9:41 AM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

Show 10 quoted lines

>> One lessor key phrase above is "so far", I think, and another one
>> you forgot to use is s/which requires/that we know &/, which to me
>> is a more serious one.  IOW, I do think it is premature for us to
>> say that that config split issue is the only thing, or to say that
>> the issue is best solved by changing the layout in the way being
>> discussed; the multiple-worktree feature needs more lab experience
>> for us to gain confidence.
>
> As a heavy user of the git-new-worktree "hack / script", is there
> something I can do to help "get more experience"?

You can try out "git worktree" command (in "lab" environment) and see what's missing, what use cases of yours it does not support.

-- 
Duy