Messages in this thread | | | Date | Fri, 11 Mar 2011 19:37:11 +0100 | From | Sam Ravnborg <> | Subject | Re: kernel git bisect question |
| |
On Fri, Mar 11, 2011 at 01:31:53PM -0500, Mark Hounschell wrote: > On 03/10/2011 04:54 PM, Steven Rostedt wrote: > > On Thu, Mar 10, 2011 at 03:27:00PM -0500, Mark Hounschell wrote: > >> Between git bisect [good | bad ]s should I always "make clean" or can I > >> count on the build system to take care of everything properly? > > > > I'm trying to bisect between 2.6.35 and 2.6.36. What have I done wrong? > Here is exactly what I've done. Why after my second "git bisect bad" do > I get a Makefile for 2.6.35-rc1 and then after the fourth I get a Makefile > for 2.6.34??
The development is not linear. So you see a commit developed on top of 2.6.34 that was included in 2.6.35. This is normal.
Sam
| |