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

Re: [PATCH] bisect reset: Allow resetting to any commit, not just a branch

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 13, 2009, 07:01 UTC
Message-ID
<7v3a5n3hgn.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4AD420BC.5060506@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
> In my workflow, after I've found the bad commit, I always want bisect to
> stay at the commit that it found. I don't want it to warp me somewhere
> else; I want to make the decision where to go next myself.
Are you sure about what you are saying?

Half of the time, the commit you test in your "git bisect" section would be a "good" one, and immediately after you tell it "bisect good", it tells you that some _other_ commit you marked "bad" is the first bad commit. In such a case, you won't be on the commit that the bisect has found.

So I _do_ agree that you would always want to stare at the commit that is the first bad one, leaving the bisection session at the detached HEAD state bisection session ends at is _totally_ different from what you want.

Previous: Johannes SixtNext: Johannes Sixt
Message 15 of 18 in “bisect reset: Allow resetting to any commit, not just a branch”
  1. bisect reset: Allow resetting to any commit, not just a branchAnders Kaseorg, Oct 12, 2009
  2. Junio C HamanoOct 12, 2009
  3. Anders KaseorgOct 12, 2009
  4. Junio C HamanoOct 12, 2009
  5. Johannes SixtOct 13, 2009
  6. Junio C HamanoOct 13, 2009
  7. Anders KaseorgOct 13, 2009
  8. bisect reset: Allow resetting to any commit, not just a branchAnders Kaseorg, Oct 13, 2009
  9. Christian CouderOct 13, 2009
  10. Anders KaseorgOct 13, 2009
  11. Christian CouderOct 13, 2009
  12. bisect reset: Allow resetting to any commit, not just a branchAnders Kaseorg, Oct 13, 2009
  13. Junio C HamanoOct 14, 2009
  14. Johannes SixtOct 13, 2009
  15. Junio C HamanoOct 13, 2009
  16. Johannes SixtOct 13, 2009
  17. Junio C HamanoOct 13, 2009
  18. Anders KaseorgOct 13, 2009

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.