From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: [PATCH, next version] git bisect: introduce 'fixed' and 'unfixed' Date: Sat, 28 Jun 2008 10:52:19 -0700 Message-ID: <7v4p7do3ak.fsf@gitster.siamese.dyndns.org> References: <20080624163810.GA4654@sigill.intra.peff.net> <20080624174157.GB9500@sigill.intra.peff.net> <7vej6mbh3w.fsf@gitster.siamese.dyndns.org> <7vprq2o4zb.fsf@gitster.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeff King , git@vger.kernel.org To: Johannes Schindelin X-From: git-owner@vger.kernel.org Sat Jun 28 19:53:33 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1KCec6-0005cO-PA for gcvg-git-2@gmane.org; Sat, 28 Jun 2008 19:53:31 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753281AbYF1Rwe (ORCPT ); Sat, 28 Jun 2008 13:52:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753235AbYF1Rwe (ORCPT ); Sat, 28 Jun 2008 13:52:34 -0400 Received: from a-sasl-fastnet.sasl.smtp.pobox.com ([207.106.133.19]:59365 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753173AbYF1Rwd (ORCPT ); Sat, 28 Jun 2008 13:52:33 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 3045312591; Sat, 28 Jun 2008 13:52:32 -0400 (EDT) Received: from pobox.com (ip68-225-240-77.oc.oc.cox.net [68.225.240.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 73F051258E; Sat, 28 Jun 2008 13:52:27 -0400 (EDT) In-Reply-To: (Johannes Schindelin's message of "Sat, 28 Jun 2008 14:48:55 +0100 (BST)") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) X-Pobox-Relay-ID: FB8ED276-453A-11DD-91BB-CE28B26B55AE-77302942!a-sasl-fastnet.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Johannes Schindelin writes: >> Johannes Schindelin 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? > > It has a "BAD" and a "GOOD" variable that are reset to "fixed" and > "unfixed" if the user said "fixed" or "unfixed". Ah, Ok, you did not mean "this is meant to applied to 'next' branch", but meant "[PATCH v$N]" for some N > 1. > But that, together with the visualize part, would take more time than I am > willing to spend on this issue. Other people would find itch (or they may not). Either way is fine.