Re: [RFC PATCH 0/1] worktree list: add --merged and --no-merged

From: Harald Nordgren <haraldnordgren@gmail.com>
Date: Oct 22, 2026, 07:21 UTC
Message-ID: <CAHwyqnXRHBTt6AoZH=OBhd9Q4UgCk6vuHqrJbog3ZYguq694HQ@mail.gmail.com>
In-Reply-To: <xmqqbj8mln3c.fsf@gitster.g>

Show 10 quoted lines

> > I noticed that I can't check out a branch that is checked out in
> > another worktree. Which seems a bit ridiculous because two regular
> > repos of the same upstream would never enforce that.
>
> Because your repository updating what commit your 'main' points at
> would not affect my repository if they track the same upstream.
>
> Worktrees are different.  If you allow your two worktrees to check
> out the same 'main', and one of them makes a commit on top, you know
> what happens, right?

I didn't. I read up on it now, and yes it's hairy. I withdraw my point here.

Show 5 quoted lines

> > AI loves worktress, so I suspect we'll see more of these discussions
> > in the future.
>
> I think that was asked and answered already.  "worktree add -d" is
> your friend.

Ok.

Harald