From: Sam Vilain <sam@vilain.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: RFE: "git bisect reverse"
Date: Wed, 27 May 2009 15:00:02 +1200 [thread overview]
Message-ID: <4A1CACB2.7000702@vilain.net> (raw)
In-Reply-To: <4A1C6B70.4050501@zytor.com>
H. Peter Anvin wrote:
> 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...
>
Oh, yes. And another thing: 'git bisect run' / 'git bisect skip'
doesn't do a very good job of skipping around broken commits (ie when
the script returns 126). It just seems to move to the next one; it
would be much better IMHO to first try the commit 1/3rd of the way into
the range, then if that fails, the commit 2/3rd of the way through it, etc.
Sam.
next prev parent reply other threads:[~2009-05-27 3:00 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 [this message]
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
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=4A1CACB2.7000702@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.