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:21 UTC
Message-ID
<7vbpkb21yp.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4AD42203.6030802@viscovery.net>
Johannes Sixt <j.sixt@viscovery.net> writes:
Show 6 quoted lines
> The situation that I'm faced quite frequently is that after I find a
> regression, I cannot tell which released version did not have the
> breakage. Hence, the first thing I have to do is to find a good commit.
> Therefore, I jump around in ancient history until I find a good commit.
> Then I start bisect. I certainly do NOT want to be warped back to this
> ancient commit by 'bisect reset'.

Unlike your other message, now, I can see _this_ one making sense very much.

It is a very good explanation as to why BISECT_START (whose sole purpose is to go back there) is not a very useful concept. What you wrote deserve to go to the "bisect reset" documentation to explain what the optional <branch> argument (perhaps we would make it a <commit> with Anders's patch) is good for and how it is intended to be used.

Previous: Johannes SixtNext: Anders Kaseorg
Message 6 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.