Messages in this thread | | | Date | Wed, 6 Jan 2010 17:53:19 -0600 | Subject | Re: Memory probing fails after 2.6.30 (bisected) | From | Robert Hancock <> |
| |
On Wed, Jan 6, 2010 at 2:32 AM, Anders Eriksson <aeriksson@fastmail.fm> wrote: > > hancockrwd@gmail.com said: >> Think you missed posting which was the actual bad commit it reported? > > The last one in the list: > 8ecee4620e76aae418bfa0e8cc830e92cb559bbb > > That's a merge commit. How do i dig futher into that? My git-fu is lacking...
AFAIK, the bisect shouldn't land on a merge commit unless the changes in the commit itself are what are causing the problem, and the merge commit itself doesn't have any changes. Is it possible something went wrong in the bisect and one of your good/bad results was incorrect?
| |