From: tmhikaru@gmail.com
To: Florian Mickler <florian@mickler.org>,
linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: Linux 2.6.35.6
Date: Thu, 30 Sep 2010 03:38:49 -0400 [thread overview]
Message-ID: <20100930073849.GA22671@roll> (raw)
In-Reply-To: <20100930072927.77f0f79b@schatten.dmk.lab>
[-- Attachment #1: Type: text/plain, Size: 2874 bytes --]
On Thu, Sep 30, 2010 at 07:29:27AM +0200, Florian Mickler wrote:
> git-log is not that expressive here, as it only shows the history of
> current HEAD (the currently checked out version). You can post the
> output of 'git bisect log'.
> If you wanna know how the region looks like you can type 'git bisect
> visualize'.
Wow that's neat. I can't be sure I understand exactly what its saying but if
I'm looking at it right I'm in the middle of a temporary fork that was
created just after 2.6.34-rc6 and was merged with 2.6.35-rc1.
This is what my git bisect log looks like:
tm@roll:~/src/linux-2.6$ git bisect log
git bisect start
# good: [e40152ee1e1c7a63f4777791863215e3faa37a86] Linus 2.6.34
git bisect good e40152ee1e1c7a63f4777791863215e3faa37a86
# bad: [9fe6206f400646a2322096b56c59891d530e8d51] Linux 2.6.35
git bisect bad 9fe6206f400646a2322096b56c59891d530e8d51
# skip: [e0bc5d4a54938eedcde14005210e6c08aa9727e4] Merge branch 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging
git bisect skip e0bc5d4a54938eedcde14005210e6c08aa9727e4
# good: [c72ea83d39efa71bf0e3fc1125e780071a79f1bc] e1000e: Remove unnessary log message
git bisect good c72ea83d39efa71bf0e3fc1125e780071a79f1bc
# skip: [4403158ba295c8e36f6736b1bb12d0f7e1923dac] Ban ecryptfs over ecryptfs
git bisect skip 4403158ba295c8e36f6736b1bb12d0f7e1923dac
# bad: [c392c4c6dccf7c64c113b473c7eceedf25eddd51] Merge branch 'perf' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 into perf/core
git bisect bad c392c4c6dccf7c64c113b473c7eceedf25eddd51
# good: [f869097e884d8cb65b2bb7831ca57b7dffb66fdd] perf session: Make read_build_id routines look at the host_machine too
git bisect good f869097e884d8cb65b2bb7831ca57b7dffb66fdd
# bad: [b8ae30ee26d379db436b0b8c8c3ff1b52f69e5d1] Merge branch 'sched-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
git bisect bad b8ae30ee26d379db436b0b8c8c3ff1b52f69e5d1
# good: [1014cfe2fb4cdd663137aafb21448cb613dd6a7d] Merge branch 'core-locking-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
git bisect good 1014cfe2fb4cdd663137aafb21448cb613dd6a7d
# good: [3aaf51ace5975050ab43c7d4d7e439e0ae7d13d7] Merge branch 'oprofile-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
git bisect good 3aaf51ace5975050ab43c7d4d7e439e0ae7d13d7
# good: [371fd7e7a56a5c136d31aa980011bd2f131c3ef5] sched: Add enqueue/dequeue flags
git bisect good 371fd7e7a56a5c136d31aa980011bd2f131c3ef5
# bad: [e7858f52a5cb868289a72264534a1f05f3340c6c] Merge branch 'cpu_stop' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc into sched/core
git bisect bad e7858f52a5cb868289a72264534a1f05f3340c6c
Just a few more steps until we find the culprit, it said 7 revisions
remained after this bisect.
Tim McGrath
[-- Attachment #2: Type: application/pgp-signature, Size: 482 bytes --]
prev parent reply other threads:[~2010-09-30 7:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 0:36 Linux 2.6.35.6 Greg KH
2010-09-27 0:36 ` Greg KH
2010-09-27 1:00 ` Felipe Contreras
2010-09-27 1:31 ` Greg KH
2010-09-27 17:05 ` Felipe Contreras
2010-09-27 16:32 ` tmhikaru
2010-09-27 17:54 ` Greg KH
2010-09-27 19:09 ` tmhikaru
2010-09-27 19:51 ` Florian Mickler
2010-09-27 23:39 ` tmhikaru
2010-09-28 4:45 ` tmhikaru
2010-09-28 6:35 ` Florian Mickler
2010-09-28 19:03 ` tmhikaru
2010-09-29 7:29 ` Florian Mickler
2010-09-29 11:02 ` tmhikaru
2010-09-29 11:33 ` Miguel Ojeda
2010-09-29 11:52 ` Florian Mickler
2010-09-29 12:19 ` Florian Mickler
2010-09-30 1:33 ` tmhikaru
2010-09-30 5:29 ` Florian Mickler
2010-09-30 7:38 ` tmhikaru [this message]
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=20100930073849.GA22671@roll \
--to=tmhikaru@gmail.com \
--cc=florian@mickler.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox