Re: Why can't I use git-bisect to find the first *good* commit?
- From
Andrew Garber <andrew@andrewgarber.com>
- Date
- Mar 28, 2011, 17:45 UTC
- Message-ID
- <AANLkTimT+WN2F-BmQzQrAs3uizHig9cCXDUdc7nQ-vC5@mail.gmail.com>
- In-Reply-To
- <vpq62r3i1z4.fsf@bauges.imag.fr>
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@grenoble-inp.fr> wrote:
Show 24 quoted lines
> Andrew Garber <andrew@andrewgarber.com> writes: > >> 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/ >