Hi, On Tue, 24 Jun 2008, Michael Haggerty wrote: > Johannes Schindelin wrote: > > 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'. > > > > So introduce the commands 'git bisect fixed' and 'git bisect unfixed'. > > It seems to me that your problem is that git-bisect requires the "good" > revision to be older than the "bad" one. If this requirement were > removed, would there still be a need for "fixed" vs. "unfixed"? Nope. The thing that makes "fixed" and "bad" special is that _one_ commit introduced that. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
