Re: [PATCH, next version] git bisect: introduce 'fixed' and 'unfixed'

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 27, 2008, 23:03 UTC
Message-ID: <7vprq2o4zb.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <alpine.DEB.1.00.0806271446180.9925@racer>

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.