rj/bisect-already-used-branch (was Re: What's cooking in git.git (Mar 2023, #02; Tue, 7))
- From
Rubén Justo <rjusto@gmail.com>
- Date
- Mar 11, 2023, 10:24 UTC
- Message-ID
- <ce31ee34-df93-5824-d7a8-5a0e19498d77@gmail.com>
- In-Reply-To
- <xmqq4jqww660.fsf@gitster.g>
Show 7 quoted lines
> * rj/bisect-already-used-branch (2023-01-22) 1 commit > (merged to 'next' on 2023-03-06 at 3508814a41) > + bisect: fix "reset" when branch is checked out elsewhere > > Allow "git bisect reset [name]" to check out the named branch (or > the original one) even when the branch is already checked out in a > different worktree linked to the same repository.
Maybe we can still adjust this to a more accurate description of the current state in this series, something like:
Allow "git bisect reset" to check out the original branch when the branch is already checked out in a different worktree linked to the same repository.