From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933331AbYEHWfu (ORCPT ); Thu, 8 May 2008 18:35:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754692AbYEHWfi (ORCPT ); Thu, 8 May 2008 18:35:38 -0400 Received: from smtpq2.tilbu1.nb.home.nl ([213.51.146.201]:47263 "EHLO smtpq2.tilbu1.nb.home.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754183AbYEHWfh (ORCPT ); Thu, 8 May 2008 18:35:37 -0400 Message-ID: <48238087.7000509@keyaccess.nl> Date: Fri, 09 May 2008 00:36:55 +0200 From: Rene Herman User-Agent: Thunderbird 2.0.0.14 (X11/20080421) MIME-Version: 1.0 To: Adrian Bunk CC: Linux Kernel , Linus Torvalds Subject: Re: GIT bisection range errors References: <48237CA0.4080001@keyaccess.nl> <20080508222545.GH22887@cs181133002.pp.htv.fi> In-Reply-To: <20080508222545.GH22887@cs181133002.pp.htv.fi> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.0 (-) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09-05-08 00:25, Adrian Bunk wrote: > On Fri, May 09, 2008 at 12:20:16AM +0200, Rene Herman wrote: >> Good day. >> >> I'm in a git bisect and am experiencing strangeness. I did a >> >> $ git checkout -b rc v2.6.26-rc1 >> $ git bisect start >> $ git bisect bad >> $ git bisect good v2.6.25 >> >> Yet, during this I'm finding myself at 2.6.25-rc6 and 2.6.25-rc8 >> as the last two results (both good...). >> >> Here's the BISECT_LOG upto this point. Is there anyone available >> who understands this well enough to be able to say from this that >> my tree is fubar? It should be a straight Linus' clone, and it's >> always pulling without trouble. >> >> git-bisect start >> # bad: [2ddcca36c8bcfa251724fe342c8327451988be0d] Linux 2.6.26-rc1 >> git-bisect bad 2ddcca36c8bcfa251724fe342c8327451988be0d >> # good: [4b119e21d0c66c22e8ca03df05d9de623d0eb50f] Linux 2.6.25 >> git-bisect good 4b119e21d0c66c22e8ca03df05d9de623d0eb50f >> # bad: [7ae44cfa7ab29b277691327e8de790d7b880722f] [ALSA] snd-powermac: style awacs.s and awacs.h >> git-bisect bad 7ae44cfa7ab29b277691327e8de790d7b880722f >> # good: [7cea51be4e91edad05bd834f3235b45c57783f0d] security: fix up documentation for security_module_enable >> git-bisect good 7cea51be4e91edad05bd834f3235b45c57783f0d >> # bad: [8f19ca1341a6d89bd96e2e69e6e10f46d3258089] x86: unify gfp masks >> git-bisect bad 8f19ca1341a6d89bd96e2e69e6e10f46d3258089 >> # good: [f49e1aa133c2c9b74b5dfddca8863609bbda9086] [NETFILTER]: nf_conntrack_sip: update copyright >> git-bisect good f49e1aa133c2c9b74b5dfddca8863609bbda9086 >> # good: [0b18542b7f5379e052d2a3132be91185776e7ceb] [NET]: Sink IPv6 menuoptions into its own submenu >> git-bisect good 0b18542b7f5379e052d2a3132be91185776e7ceb > > Don't trust any dates you see in git. ;-) > > The last commit in your list was added to David's tree at around the > time Linus released Linux 2.6.25-rc7. > > But David's tree was merged into Linus' tree after 2.6.25. > > So actually everything is fine. Well, thanks for the reply and I'm going forward for now, but the Makefile is actually calling this 2.6.25-rc8. My next "git bisect good" after the above landed me now after 2.6.25 according to the Makefile. It could just be a tags issue I guess, where my tree is confused about what tag belongs to v2.6.25? (new two lines in the log) # good: [ba380013b681e91e059f95b51002f8d43024b371] b43: Add fastpath to b43_mac_suspend() git-bisect good ba380013b681e91e059f95b51002f8d43024b371 Rene.