Hi, On Fri, 27 Jun 2008, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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". > Aside from the 'visualize' issue this does not attempt to address, Yes, I forgot about that issue, mainly because I do not use it myself... > 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. Hmm. I tried to avoid that, as it would mean a larger patch. But I guess you could write .git/BISECT_TERMS or some such. But that, together with the visualize part, would take more time than I am willing to spend on this issue. Well, I guess I'll leave it then, 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
