Re: [RFE] allow git bisect to figure out in which revision a bug was fixed

From: Nicolas Pitre <nico@cam.org>
Date: Jul 22, 2009, 00:35 UTC
Message-ID: <alpine.LFD.2.00.0907212030180.30629@xanadu.home>
In-Reply-To: <7vprbtbwhu.fsf@alter.siamese.dyndns.org>

On Tue, 21 Jul 2009, Junio C Hamano wrote:

Show 11 quoted lines

> There indeed was discussions along the line of adding "fixed" and "broken"
> as synonyms to "bad" and "good".
> 
> I mildly suspect that it is a matter of opinion if such an addition would
> make things better or more confusing, because the word "broken" feels more
> strongly associated with "bad" than "good".
> 
> Perhaps "wanted" and "unwanted" makes a better pair of more neutral words?
> In bisect, we do not want to judge commits' in absolute goodness scale.
> It is all relative to what _you_ as the person who runs bisect want, and
> in that sense the original terminology "good/bad" was suboptimal.

It is short which is good.

Why not simply automatically inverting the meaning of good and bad based on which commit is the ancestor of the other initially?

Nicolas