From: Aniket Gupta <aniketgupta3001@gmail.com>
To: ps@pks.im
Cc: toon@iotcl.com, phillip.wood@dunelm.org.uk, nikita@nbobko.com,
git@vger.kernel.org
Subject: Re: git-history(1) fixup broken with worktrees?
Date: Fri, 20 Nov 2026 22:07:12 +0530 [thread overview]
Message-ID: <20261120163712.64814-1-aniketgupta3001@gmail.com> (raw)
In-Reply-To: <aob_LsfI9cO3PewF@pks.im>
Hi Patrick,
> I've created an issue [1] for this scheduled for the next release cycle.
> Happy if anybody else beats us to it though.
It seems nobody has picked this up. Can I send a patch so that git history refuses to update a branch that is checked out in another worktree or is getting rebased when the update would change its tree? This should cover Nikita's report.
Thanks,
Aniket
prev parent reply other threads:[~2026-11-20 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 18:54 git-history(1) fixup broken with worktrees? Toon Claes
2026-07-18 9:31 ` Phillip Wood
2026-07-28 13:44 ` Toon Claes
2026-08-20 13:20 ` Patrick Steinhardt
2026-11-20 16:37 ` Aniket Gupta [this message]
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=20261120163712.64814-1-aniketgupta3001@gmail.com \
--to=aniketgupta3001@gmail.com \
--cc=git@vger.kernel.org \
--cc=nikita@nbobko.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
--cc=toon@iotcl.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