From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: RFE: "git bisect reverse"
Date: Wed, 27 May 2009 22:26:01 +0200 [thread overview]
Message-ID: <vpqprdue1ie.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20090527172233.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Wed\, 27 May 2009 17\:22\:33 +0900")
Nanako Shiraishi <nanako3@lavabit.com> writes:
> Quoting "H. Peter Anvin" <hpa@zytor.com>:
>
>> I would like to request the following feature:
>>
>> "git bisect reverse"
>>
>> ... does exactly the same thing as "git bisect start", except that it
>> flips the meaning of "good" and "bad". It is mentally fairly taxing to
>> do a reverse bisection (looking for an antiregression) when one has to
>> flip the meaning of "good" and "bad" (which are very loaded words to our
>> psyche), and it's even worse to try to get a user to do it...
>
> There was a discussion on "fixed" and "unfixed" aliases to find a commit that fixed an old breakage.
>
> http://thread.gmane.org/gmane.comp.version-control.git/86063/focus=86563
I think the bzr "bisect" plugin uses "yes" and "no" instead for this
reason. I find it mentally easier to adapt it to both cases ("yes,
it's fixed" or "yes, it's broken" depending on what you search).
--
Matthieu
prev parent reply other threads:[~2009-05-27 20:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 22:21 RFE: "git bisect reverse" H. Peter Anvin
2009-05-27 3:00 ` Sam Vilain
2009-05-27 4:20 ` H. Peter Anvin
2009-05-27 5:26 ` Christian Couder
2009-05-27 21:11 ` Ealdwulf Wuffinga
2009-05-27 21:18 ` Clemens Buchacher
2009-05-27 22:07 ` Ealdwulf Wuffinga
2009-05-27 23:08 ` Sam Vilain
2009-05-28 20:29 ` Ealdwulf Wuffinga
2009-05-29 4:20 ` Sam Vilain
2009-05-31 22:41 ` Ealdwulf Wuffinga
2009-05-28 3:11 ` H. Peter Anvin
2009-05-28 21:07 ` Ealdwulf Wuffinga
2009-05-28 21:54 ` H. Peter Anvin
2009-05-31 22:18 ` Ealdwulf Wuffinga
2009-05-27 20:11 ` Christian Couder
2009-05-27 8:22 ` Nanako Shiraishi
2009-05-27 20:26 ` Matthieu Moy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqprdue1ie.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=nanako3@lavabit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).