From: Jan Kara <jack@suse.cz>
To: Peter Harris <git@peter.is-a-geek.org>
Cc: git@vger.kernel.org
Subject: Re: git bisect goes wild?
Date: Tue, 24 Feb 2009 20:10:02 +0100 [thread overview]
Message-ID: <20090224191002.GF22108@duck.suse.cz> (raw)
In-Reply-To: <eaa105840902241059y70143c43s7d12b10fe35127e6@mail.gmail.com>
On Tue 24-02-09 13:59:16, Peter Harris wrote:
> 2009/2/24 Jan Kara:
> > Hi,
> >
> > I've been bisecting some change in Linux kernel. The output of
> > "git bisect log" is:
> ...
> > git-bisect bad 419217cb1d0266f62cbea6cdc6b1d1324350bc34
> ...
> > git-bisect good 3e9830dcabdeb3656855ec1b678b6bcf3b50261c
> >
> > But after the last command, I was sent to commit
> > 9ec76fbf7d6da3e98070a7059699d0ca019b0c9b which is far outside the window
> > between the last good and bad commit.
>
> How did you determine that this commit is outside the window?
>
> When I run "gitk 3e9830..419217" it shows that commit, as does "git
> log". 9ec76fb appears to be inside the window to me.
Ho, hum, right. But if I do:
git describe 9ec76fbf7d6da3e98070a7059699d0ca019b0c9b
I get v2.6.23-rc3-215-g9ec76fb which is a bit strange for bisecting
between 2.6.23 and 2.6.24. Also the kernel gets named 2.6.23-rc3 and kernel
config options get also to some pre 2.6.23 state. That's what is confusing
me. It seems like the kernel checked out is some old one. I'm not a git
expert so it might be fine but it just seems really strange.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2009-02-24 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 18:44 git bisect goes wild? Jan Kara
2009-02-24 18:59 ` Peter Harris
2009-02-24 19:10 ` Jan Kara [this message]
2009-02-24 19:14 ` Teemu Likonen
2009-02-24 19:28 ` Jan Kara
2009-02-24 19:46 ` Daniel Barkalow
2009-02-24 20:04 ` Jan Kara
2009-02-24 21:15 ` Daniel Barkalow
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=20090224191002.GF22108@duck.suse.cz \
--to=jack@suse.cz \
--cc=git@peter.is-a-geek.org \
--cc=git@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.