If branch bar is broken, do a bisect on branch bar. The fact that branch foo works in inconsequential. On Mon, Mar 28, 2011 at 1:33 PM, Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > Andrew Garber <andrew@xxxxxxxxxxxxxxxx> writes: > >> On Mon, Mar 28, 2011 at 10:40 AM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: >> >>> Â Â Âo--o--o--B >>> Â Â / >>> Â--o--o--o--o--G >>> >>> When I have this history and I mark B as bad and G as good, will I now >>> find the first bad or the first good commit? >> >> That kind of situation shouldn't occur: IMO, bisect should only deal >> with a single branch (the current branch). > > Why? > > It's not uncommon in real life to face the "it works in branch foo but > not in branch bar, where did it break?" problem. And one expects a great > tool such as Git to be able to answer it. > > -- > Matthieu Moy > http://www-verimag.imag.fr/~moy/ > -- 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