From: Mark Hounschell <markh@compro.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: kernel git bisect question
Date: Fri, 11 Mar 2011 13:41:30 -0500 [thread overview]
Message-ID: <4D7A6CDA.4070402@compro.net> (raw)
In-Reply-To: <20110311183711.GA559@merkur.ravnborg.org>
On 03/11/2011 01:37 PM, Sam Ravnborg wrote:
> 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.
>
OK, thanks again. I'll continue on with the process then.
Mark
next prev parent reply other threads:[~2011-03-11 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 20:27 kernel git bisect question Mark Hounschell
2011-03-10 21:14 ` Sam Ravnborg
2011-03-10 21:17 ` Mark Hounschell
2011-03-10 21:54 ` Steven Rostedt
2011-03-11 18:31 ` Mark Hounschell
2011-03-11 18:37 ` Sam Ravnborg
2011-03-11 18:41 ` Mark Hounschell [this message]
2011-03-11 18:51 ` Steven Rostedt
2011-03-11 18:56 ` Mark Hounschell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7A6CDA.4070402@compro.net \
--to=markh@compro.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.