Re: Why can't I use git-bisect to find the first *good* commit?
- From
Andrew Garber <andrew@andrewgarber.com>
- Date
- Mar 28, 2011, 18:12 UTC
- Message-ID
- <AANLkTinuH4Ut+jtdqRfFrNeXA6JmBK2i0ddCcz4vV6JC@mail.gmail.com>
- In-Reply-To
- <vpqr59r6sg5.fsf@bauges.imag.fr>
On Mon, Mar 28, 2011 at 1:55 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
> Then which commit do you specify as "good"?
Any ancestral commit *on the same branch* which is know to be working. Isn't the whole point of git bisect is to do binary search through time? It only makes sense to me to use it on a single branch at a time. Perhaps you could give a concrete example of where you could use it for multiple branches simultaneously?