From: Jeff King <peff@peff.net>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: git rebase issue
Date: Mon, 20 Mar 2023 13:01:58 -0400 [thread overview]
Message-ID: <20230320170158.GA2614670@coredump.intra.peff.net> (raw)
In-Reply-To: <CAHp75Vc419vikJ184syJHN7rxyaspHzgtT9a_uFA=CT=cdqo-w@mail.gmail.com>
[Please don't put random folks in the to/cc unless you think they have
specific knowledge related to your problem.]
On Mon, Mar 20, 2023 at 02:10:38PM +0200, Andy Shevchenko wrote:
> > > With the new release I have got an error
> > >
> > > fatal: 'netboot' is already checked out at ...
> > >
> > > To work around this I have to split the above to
> > >
> > > git checkout --ignore-other-worktrees "$branch"
> > > git rebase --rebase-merges -X ours --onto "$newbase" "$oldbase"
> > >
> > > which makes all these too inconvenient.
> > >
> > > Any suggestions?
>
> So, what should I do? Today I got again to help manually with my (used
> to working) scripts.
Running "git log --grep=already.checked.out" suggests that it may be
b5cabb4a967 (rebase: refuse to switch to branch already checked out
elsewhere, 2020-02-23).
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).
-Peff
next prev parent reply other threads:[~2023-03-20 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 12:35 git rebase issue Andy Shevchenko
2023-03-13 12:58 ` Andy Shevchenko
2023-03-20 12:10 ` Andy Shevchenko
2023-03-20 14:41 ` Felipe Contreras
2023-03-20 17:01 ` Jeff King [this message]
2023-03-20 17:20 ` Andy Shevchenko
2023-03-23 20:37 ` Felipe Contreras
2023-03-24 7:52 ` Andy Shevchenko
2025-03-22 13:42 ` Andy Shevchenko
2025-03-23 1:37 ` Eric Sunshine
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 17:53 Git Rebase Issue Pierre-Luc Loyer
2015-12-22 19:25 ` Junio C Hamano
2015-12-22 21:02 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230320170158.GA2614670@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=andy.shevchenko@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).