From: Paolo Ornati <ornati@gmail.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes
Date: Wed, 1 Sep 2010 20:47:16 +0200 [thread overview]
Message-ID: <20100901204716.775e9cfd@gmail.com> (raw)
In-Reply-To: <201008312153.45792.Martin@lichtvoll.de>
On Tue, 31 Aug 2010 21:53:43 +0200
Martin Steigerwald <Martin@lichtvoll.de> wrote:
> Obviously I am not interested in kernels prior 2.6.33. Should I just do a
> "git bisect good" without trying the kernel or is there some other remedy?
No. Git is right in asking you to test that commit: you are ignoring
branches and merges.
Example
========
Linus Tree Usb Tree
v2.6.33-rc2
| \
| | commit A (version is v2.6.33-rc2)
| | commit B ( " )
v2.6.33 | commit C ( " )
| __/
| __/
| __/
|_/
X <--- MERGE
So the commit you are testing it's like "commit A": it was done before
(in time) v2.6.33, on a kernel based on v2.6.33-rc2, but was merged in
Linus' tree _after_ v2.3.33.
So this this behaviour is normal :)
--
Paolo Ornati
Linux 2.6.35.4 on x86_64
next prev parent reply other threads:[~2010-09-01 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 19:53 help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes Martin Steigerwald
2010-08-31 22:39 ` Ken Moffat
2010-09-01 16:10 ` Martin Steigerwald
2010-09-01 18:13 ` Ken Moffat
2010-09-01 18:47 ` Paolo Ornati [this message]
2010-09-01 19:26 ` Martin Steigerwald
2010-09-05 7:53 ` Martin Steigerwald
2010-09-05 12:20 ` Paolo Ornati
2010-09-05 13:25 ` Martin Steigerwald
2010-09-07 2:51 ` Ted Ts'o
2010-09-09 14:18 ` Martin Steigerwald
2010-09-10 11:55 ` Florian Mickler
2010-09-10 13:49 ` Martin Steigerwald
2010-09-10 15:53 ` Theodore Tso
2010-09-10 16:18 ` Martin Steigerwald
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=20100901204716.775e9cfd@gmail.com \
--to=ornati@gmail.com \
--cc=Martin@lichtvoll.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 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.