git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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.
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 4 in “What's cooking in git.git (Mar 2023, #02; Tue, 7)”
  1. Junio C HamanoMar 7, 2023
  2. rj/bisect-already-used-branch (was Re: What's cooking in git.git (Mar 2023, #02; Tue, 7))Rubén Justo, Mar 11, 2023
  3. Junio C HamanoMar 11, 2023
  4. rj/branch-unborn-in-other-worktrees (was What's cooking in git.git (Mar 2023, #02; Tue, 7))Rubén Justo, Mar 11, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.