From: "Tony Luck" <tony.luck@intel.com>
To: "Greg Lee" <glee@casabyte.com>
Cc: sean <seanlkml@sympatico.ca>, git@vger.kernel.org
Subject: Re: Problem with git bisect between 2.6.15 and 2.6.16
Date: Mon, 27 Mar 2006 16:22:33 -0800 [thread overview]
Message-ID: <12c511ca0603271622n6e4614b2s6f936469863efd9d@mail.gmail.com> (raw)
In-Reply-To: <0e7e01c651fc$e30a2860$a100a8c0@casabyte.com>
> No, the problem was fixed in 2.6.16 and I'm trying to figure out what fixed it so that I
> can back-port the fix into a previous kernel version, so 2.6.16 is good and 2.6.15 is bad.
You'll need to invert "good" and bad" for this. I.e. mark 2.6.15 as
good, 2.6.16 as bad, and
then as you test mark kernels with the bug as good, and ones without
as bad. Try not to go
insane while working in this inverted parallel universe :-)
-Tony
next prev parent reply other threads:[~2006-03-28 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:00 Problem with git bisect between 2.6.15 and 2.6.16 Greg Lee
[not found] ` <20060327190627.7d72794f.seanlkml@sympatico.ca>
2006-03-28 0:06 ` sean
2006-03-28 0:16 ` Greg Lee
2006-03-28 0:22 ` Tony Luck [this message]
2006-03-29 19:28 ` Greg Lee
-- strict thread matches above, loose matches on Subject: below --
2006-03-29 19:43 Luck, Tony
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=12c511ca0603271622n6e4614b2s6f936469863efd9d@mail.gmail.com \
--to=tony.luck@intel.com \
--cc=git@vger.kernel.org \
--cc=glee@casabyte.com \
--cc=seanlkml@sympatico.ca \
/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).