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

From: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Feb 1, 2016, 02:41 UTC
Message-ID: <jwvfuxd17bz.fsf-monnier+gmane.comp.version-control.git@gnu.org>
In-Reply-To: <xmqqh9htya2e.fsf@gitster.mtv.corp.google.com>

Show 7 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"?

        Stefan

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.