Re: git rebase issue

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Mar 23, 2023, 20:37 UTC
Message-ID: <CAMP44s2hEudOpOcyXzZQNYtQSHXOd4NiPBboH=90RHEgF_Lamg@mail.gmail.com>
In-Reply-To: <CAHp75VeMoXZdr++6BiOMhOnSqm5rPe+t0bNzpLJsCuGp8NU=wA@mail.gmail.com>

On Mon, Mar 20, 2023 at 12:11 PM Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Mon, Mar 20, 2023 at 7:02 PM Jeff King <peff@peff.net> wrote:

Show 8 quoted lines

> > Adding its author to the cc, who may be able to say more. But my
> > understanding is that this was probably fixing a bug (though I don't
> > know all the implications of having a branch checked out in multiple
> > worktrees).
>
> Note, in my case it's "checked" in the BARE repository, which means
> it's actually not.
> This case shouldn't be an impediment or racy AFAIU.

In that case I agree it should work, but when I tried to reproduce the issue the bare repository is ignored, only worktrees are considered.

Are you sure the branch isn't checked out in other worktree(s)?

-- 
Felipe Contreras