From: John Tapsell <johnflux@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: More git bisect modes
Date: Thu, 5 Mar 2009 09:49:26 +0000 [thread overview]
Message-ID: <43d8ce650903050149u4ca98444w28efceb9084efa68@mail.gmail.com> (raw)
Hi,
Although "git bisect" is called, well, bisect, it would be nice to
have other modes.
* A completely linear version - check every version. Particularly
useful after rebasing to make sure all the commits still compile.
* An allow-for-mistakes-bisect. This would use a bisection technique
that would allow for a minimum of 1 mistake when marking a commit good
or bad. This point isn't particularly to help those with fat fingers,
but for bugs that are subtle and for bugs that are caused by multiple
commits. (I can go into the details of how to do such a bisect
later).
* An exponential back-off. Typically I know that HEAD is broken, and
I don't know when it used to work. It would be nice to exponentially
go back through the commits to find the first working commit, then
bisect from there.
Before I start working on the code for any of these, do people like
this? Would this fit into the 'git bisect' command?
John
next reply other threads:[~2009-03-05 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 9:49 John Tapsell [this message]
2009-03-05 10:05 ` More git bisect modes Nanako Shiraishi
2009-03-05 10:17 ` John Tapsell
2009-03-05 10:31 ` Junio C Hamano
2009-03-05 11:09 ` bisect run, was " Johannes Schindelin
2009-03-05 11:18 ` John Tapsell
2009-03-05 11:31 ` Johannes Schindelin
2009-03-05 20:59 ` Christian Couder
2009-03-05 20:53 ` Christian Couder
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=43d8ce650903050149u4ca98444w28efceb9084efa68@mail.gmail.com \
--to=johnflux@gmail.com \
--cc=git@vger.kernel.org \
/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).