On 8/17/2013 4:24 PM, Christopher M. Penalver wrote:
> John Hupp, the next step is to commit bisect from 3.7.0-7.15 to
> 3.8.0-0.2 in order to identify the commit that caused this problem via
> https://wiki.ubuntu.com/Kernel/KernelBisection .
>
That instruction has a FAQ about how to proceed when git bisect start
generates "Bisecting: a merge base must be tested," but it seems to
assume that one has completed at least one git bisect start. How do I
proceed if that is the result with the very first attempt?
On 8/17/2013 4:24 PM, Christopher M. Penalver wrote: /wiki.ubuntu. com/Kernel/ KernelBisection .
> John Hupp, the next step is to commit bisect from 3.7.0-7.15 to
> 3.8.0-0.2 in order to identify the commit that caused this problem via
> https:/
>
That instruction has a FAQ about how to proceed when git bisect start
generates "Bisecting: a merge base must be tested," but it seems to
assume that one has completed at least one git bisect start. How do I
proceed if that is the result with the very first attempt?