git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH, next version] git bisect: introduce 'fixed' and 'unfixed'
Date: Fri, 27 Jun 2008 16:03:36 -0700	[thread overview]
Message-ID: <7vprq2o4zb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0806271446180.9925@racer> (Johannes Schindelin's message of "Fri, 27 Jun 2008 14:48:31 +0100 (BST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> When you look for a fix instead of a regression, it can be quite hard
> to twist your brain into choosing the correct bisect command between
> 'git bisect bad' and 'git bisect good'.

Hmm, I do not currently see any differene between master and next version
of bisect.  In what way is this 'next' version?

Aside from the 'visualize' issue this does not attempt to address, I
wonder if it may be a good idea to detect and warn mixed usage as well
(e.g. "You earlier said 'bad' but now you are saying 'fixed' -- are you
sure?"), and if so if it can be implemented easily.

  reply	other threads:[~2008-06-27 23:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 14:17 [TOY PATCH] git bisect: introduce 'fixed' and 'unfixed' Johannes Schindelin
2008-06-24 14:42 ` Stephan Beyer
2008-06-24 14:55   ` Johannes Schindelin
2008-06-24 15:16     ` Stephan Beyer
2008-06-24 15:02 ` Nicolas Pitre
2008-06-24 16:38 ` Jeff King
2008-06-24 16:50   ` Johannes Schindelin
2008-06-24 17:09     ` [NON-TOY " Johannes Schindelin
2008-06-24 17:41       ` Jeff King
2008-06-24 19:22         ` Daniel Barkalow
2008-06-24 19:26           ` Johannes Schindelin
2008-06-24 22:30         ` Junio C Hamano
2008-06-27 13:48           ` [PATCH, next version] " Johannes Schindelin
2008-06-27 23:03             ` Junio C Hamano [this message]
2008-06-28 13:48               ` Johannes Schindelin
2008-06-28 17:52                 ` Junio C Hamano
2008-06-24 19:59       ` [NON-TOY PATCH] " SZEDER Gábor
2008-06-24 20:06       ` Michael Haggerty
2008-06-24 20:38         ` Johannes Schindelin
2008-06-24 22:31           ` Junio C Hamano
2008-06-24 22:43             ` Nicolas Pitre
2008-06-26  6:03             ` Christian Couder
2008-06-24 22:48         ` Lea Wiemann
2008-06-24 23:53           ` A Large Angry SCM
2008-06-25  7:27             ` Karl Hasselström
2008-06-24 16:54   ` [TOY " Reini Urban

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vprq2o4zb.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).