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:18 UTC
- Message-ID
- <AANLkTinC9Lr9uCTUZSVxVR56+FQm2NGRpPu90fm9OHF5@mail.gmail.com>
- In-Reply-To
- <4D909DD1.2050904@viscovery.net>
On Mon, Mar 28, 2011 at 10:40 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
Show 11 quoted lines
> Define "end" and "other end"! It's not that trivial. > > 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? > > -- Hannes >
That kind of situation shouldn't occur: IMO, bisect should only deal with a single branch (the current branch).