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

Re: [RFC/PATCH]: reverse bisect v 2.0

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 4, 2011, 23:27 UTC
Message-ID
<7v62k4ban7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<201110050034.46334.chriscool@tuxfamily.org>
Christian Couder <chriscool@tuxfamily.org> writes:
Show 6 quoted lines
> If we decide to go with yes/no, an option like:
>
> --yes-means=<it behaves like this>
>
> seems to me easier to understand. Though I recognize that it doesn't tell that 
> the behavior changed.
What problem are you trying to solve?

As I already said while discussing --has-property vs --used-to, I think that --yes-means shares the exact same downside as --has-property.

The --used-to proposal was to make sure that people who are bisecting to find fixes would not by mistake say

	git bisect start --used-to='work fine'

as it is very clear that bisecting in a history with something that used to work fine is _not_ hunting for a fix.

When the users say
	git bisect start --yes-means='frotz is broken'

is it clear to them that they are supposed to define what used to be the case (in which case "yes" is always mapped to "good")? If you are trying to allow them to say either old or new behaviour with --yes-means, how does your "bisect" know if it needs to map "yes" to "good" (regression hunting), or "yes" to "bad" (looking for a fix)?

Previous: Christian CouderNext: Andrew Ardill
Message 14 of 17 in “RFC: reverse bisect”
  1. Michal VyskocilSep 29, 2011
  2. Sverre RabbelierSep 29, 2011
  3. Johannes SixtSep 29, 2011
  4. Jeff KingSep 30, 2011
  5. Frans KlaverSep 30, 2011
  6. Michal VyskocilSep 30, 2011
  7. : reverse bisect v 2.0Michal Vyskocil, Sep 30, 2011
  8. Junio C HamanoSep 30, 2011
  9. Jeff KingOct 3, 2011
  10. Junio C HamanoOct 3, 2011
  11. Jeff KingOct 4, 2011
  12. Junio C HamanoOct 4, 2011
  13. Christian CouderOct 4, 2011
  14. Junio C HamanoOct 4, 2011
  15. Andrew ArdillOct 7, 2011
  16. Junio C HamanoOct 12, 2011
  17. Jeff KingOct 12, 2011

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.