Re: Why can't I use git-bisect to find the first *good* commit?
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Mar 28, 2011, 17:33 UTC
- Message-ID
- <vpq62r3i1z4.fsf@bauges.imag.fr>
- In-Reply-To
- <AANLkTinC9Lr9uCTUZSVxVR56+FQm2NGRpPu90fm9OHF5@mail.gmail.com>
Andrew Garber <andrew@andrewgarber.com> writes:
Show 11 quoted lines
> On Mon, Mar 28, 2011 at 10:40 AM, Johannes Sixt <j.sixt@viscovery.net> 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/