From: Junio C Hamano <gitster@pobox.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Jeff King <peff@peff.net>, darxus@chaosreigns.com, git@vger.kernel.org
Subject: Re: Feature request: don't require both bad and good when bisecting
Date: Mon, 19 Mar 2012 09:49:21 -0700 [thread overview]
Message-ID: <7vobrsbkoe.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4F675DD3.3040004@op5.se> (Andreas Ericsson's message of "Mon, 19 Mar 2012 17:24:51 +0100")
Andreas Ericsson <ae@op5.se> writes:
> It's sort of beside the point though. Using git as experiment (again),
> we're looking at less than 30000 revisions and 289 non-rc tags. With only
> 30k revisions, you'll do *worse* testing 15 tags sequentially than you
> would by just letting the bisection machinery get on with it and use
> the full history as base for bisection.
I think you are missing the primary point in what Jeff said.
It does not matter if you inspect increasingly older versions based on
exponentially longer strides or if you test tagged releases. What matters
is to making intelligent determination after seeing a failure, between the
failure due to "the feature being tested did not even exist" and "the
feature when introduced was good but at this commit it is broken".
prev parent reply other threads:[~2012-03-19 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 21:29 Feature request: don't require both bad and good when bisecting darxus
2012-03-19 14:45 ` Andreas Ericsson
2012-03-19 15:30 ` Jeff King
2012-03-19 16:24 ` Andreas Ericsson
2012-03-19 16:45 ` Jeff King
2012-03-19 16:49 ` Junio C Hamano [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=7vobrsbkoe.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ae@op5.se \
--cc=darxus@chaosreigns.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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