Git development
 help / color / mirror / Atom feed
From: "Frans Klaver" <fransklaver@gmail.com>
To: git@vger.kernel.org
Subject: Re: RFC: reverse bisect
Date: Fri, 30 Sep 2011 07:31:41 +0200	[thread overview]
Message-ID: <op.v2lwa4rp0aolir@keputer.lokaal> (raw)
In-Reply-To: <20110930040924.GA28724@sigill.intra.peff.net>

On Fri, 30 Sep 2011 06:09:24 +0200, Jeff King <peff@peff.net> wrote:

> One catch is that the run command assumes a successful exit is "good",
> and anything else is "bad". Which makes:
>
>   git bisect run make test
>
> good for finding regressions, but is a little counterintuitive for the
> yes/no thing (a successful exit means "no").

Then you would require a script that inverts the result, no? From my
point of view it's either that or add an option telling bisect run how
to interpret the results. In the latter case you could still consider
adding the regression/improvement qualification to bisect start. It might
help getting the mind set right.

Frans

  reply	other threads:[~2011-09-30  5:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 14:20 RFC: reverse bisect Michal Vyskocil
2011-09-29 14:42 ` Sverre Rabbelier
2011-09-29 16:27 ` Johannes Sixt
2011-09-30  4:09   ` Jeff King
2011-09-30  5:31     ` Frans Klaver [this message]
2011-09-30  8:29   ` Michal Vyskocil
2011-09-30 11:42 ` [RFC/PATCH]: reverse bisect v 2.0 Michal Vyskocil
2011-09-30 18:13   ` Junio C Hamano
2011-10-03 10:41     ` Jeff King
2011-10-03 17:00       ` Junio C Hamano
2011-10-04 10:30         ` Jeff King
2011-10-04 15:22           ` Junio C Hamano
2011-10-04 22:34             ` Christian Couder
2011-10-04 23:27               ` Junio C Hamano
2011-10-07  1:57                 ` Andrew Ardill
2011-10-12  4:57                   ` Junio C Hamano
2011-10-12 20:14                     ` Jeff King

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=op.v2lwa4rp0aolir@keputer.lokaal \
    --to=fransklaver@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