From: "Greg Lee" <glee@casabyte.com>
To: "'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 19:16:40 -0500 [thread overview]
Message-ID: <0e7e01c651fc$e30a2860$a100a8c0@casabyte.com> (raw)
In-Reply-To: <BAYC1-PASMTP036F0DBE8F7101BCAD5470AED30@CEZ.ICE>
> You need to do the bisect start after you cd into the linux-git
> directory.
Sorry, cut and paste error, I did the cd before the bisect:
[root@Fedora-test git]# git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-git-fresh
[root@Fedora-test git]# cd linux-git-fresh/
[root@Fedora-test linux-git-fresh]# git bisect start
[root@Fedora-test linux-git-fresh]# git bisect bad v2.6.15
[root@Fedora-test linux-git-fresh]# git bisect good v2.6.16
dab47a31f42a23d2b374e1cd7d0b797e8e08b23d was both good and bad
> Also, it appears you have the good and bad reversed,
> presumably the newer (v2.6.16) is bad, and the older (v.2.6.15)
> is good.
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.
Greg
next prev parent reply other threads:[~2006-03-28 0:18 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 [this message]
2006-03-28 0:22 ` Tony Luck
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0e7e01c651fc$e30a2860$a100a8c0@casabyte.com' \
--to=glee@casabyte.com \
--cc=git@vger.kernel.org \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).