From: Linus Torvalds <torvalds@linux-foundation.org>
To: Carlo Wood <carlo@alinoe.com>
Cc: Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, eric@anholt.net,
zhenyu.z.wang@intel.com, lethal@linux-sh.org,
y-goto@jp.fujitsu.com
Subject: Re: 2.6.22-rc5 regression
Date: Mon, 18 Jun 2007 11:35:03 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0706181127380.14121@woody.linux-foundation.org> (raw)
In-Reply-To: <20070618181225.GB8054@alinoe.com>
On Mon, 18 Jun 2007, Carlo Wood wrote:
>
> I suppose you mean: ... then you WILL get sensible values out of git
> bisect. But, since I already did a real "git bisect" without giving it
> random points, I am afraid you jumped conclusions.
Hey, fair enough.
That said, your "git bisect" really *does* act oddly.
> However, I can easily reproduce it. From my history file I can see that I started with:
>
> git bisect start
> git bisect bad v2.6.22-rc5
> git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
Goodie.
> I wrote everything down on paper (the git id's and whether they
> were good or bad), so I can reproduce it with:
I can follow along, but I get *totally*different* git bisection points!
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect start
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect bad v2.6.22-rc5
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
> Bisecting: 128 revisions left to test after this
> D include/asm-blackfin/macros.h
> M scripts/package/Makefile
> D scripts/package/builddeb
You seem to have a modified tree! What are those modifications to the
blackfin macros.h etc files?
You *should* have gotten this:
[torvalds@woody linux]$ git bisect start
[torvalds@woody linux]$ git bisect bad v2.6.22-rc5
[torvalds@woody linux]$ git bisect good 99f9f3d49cbc7d944476f6fde53a77ec789ab2aa
Bisecting: 127 revisions left to test after this
[9808901b6c63a1c850b072e624c228901a9eaf10] Blackfin serial driver: ignore framing and parity errors
but those are just off by one, at least (127 vs 128 commits left).
> [cf68676222e54cd0a31efd968da00e65f9a0963f] Blackfin serial driver: actually implement the break_ctl() function
> hikaru:/usr/src/kernel/git/linux-2.6>git bisect good
> Bisecting: 111 revisions left to test after this
And that's totally broken. Even if I don't use the "9808901b6" commit, and
use your "cf686762" commit, I get:
[torvalds@woody linux]$ git bisect good cf68676222e54cd0a31efd968da00e65f9a0963f
Bisecting: 63 revisions left to test after this
[aba297927d1d558c7a94548135133bdf9172708a] Merge master.kernel.org:/pub/scm/linux/kernel/git/kyle/parisc-2.6
Notice? The "127 revisions left to test after this" has become "63
revisions left to test after this".
That number should be cut in half each time. And you shouldn't get some
strange dirty tree indications.
It might be worth it just making sure your git is ok. It really is acting
oddly. What version is it?
Linus
next prev parent reply other threads:[~2007-06-18 18:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 18:22 2.6.22-rc5 regression Carlo Wood
2007-06-17 19:58 ` Carlo Wood
2007-06-17 21:49 ` Carlo Wood
2007-06-17 23:18 ` Paul Mundt
2007-06-18 0:10 ` Carlo Wood
2007-06-18 0:25 ` Paul Mundt
2007-06-18 7:01 ` Sean
2007-06-18 17:01 ` Linus Torvalds
2007-06-18 18:12 ` Carlo Wood
2007-06-18 18:15 ` Carlo Wood
2007-06-18 18:35 ` Linus Torvalds [this message]
2007-06-18 19:54 ` Carlo Wood
2007-06-18 20:42 ` Linus Torvalds
2007-06-18 22:30 ` Daniel Barkalow
2007-06-18 22:50 ` Carlo Wood
2007-06-18 22:57 ` Linus Torvalds
2007-06-19 23:37 ` Carlo Wood
2007-06-19 23:44 ` Dave Jones
2007-06-20 0:09 ` Linus Torvalds
2007-06-20 13:11 ` Carlo Wood
2007-06-20 13:31 ` Carlo Wood
2007-06-20 1:15 ` Wang Zhenyu
2007-06-20 1:42 ` Wang Zhenyu
2007-06-20 14:02 ` Carlo Wood
2007-06-20 15:46 ` Wang Zhenyu
2007-06-21 5:43 ` [PATCH][AGPGART] intel_agp: don't load if no IGD and AGP port Wang Zhenyu
2007-06-21 16:10 ` Carlo Wood
2007-06-22 0:55 ` Wang Zhenyu
2007-06-23 16:52 ` Andrew Morton
2007-06-23 18:42 ` Dave Jones
2007-06-23 18:50 ` Andrew Morton
2007-06-23 19:06 ` Dave Jones
2007-06-25 1:01 ` Wang Zhenyu
2007-06-20 13:22 ` 2.6.22-rc5 regression Carlo Wood
2007-06-20 13:58 ` Carlo Wood
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=alpine.LFD.0.98.0706181127380.14121@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=carlo@alinoe.com \
--cc=davej@redhat.com \
--cc=eric@anholt.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=y-goto@jp.fujitsu.com \
--cc=zhenyu.z.wang@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).