From: Teemu Likonen <tlikonen@iki.fi>
To: Jan Kara <jack@suse.cz>
Cc: Peter Harris <git@peter.is-a-geek.org>, git@vger.kernel.org
Subject: Re: git bisect goes wild?
Date: Tue, 24 Feb 2009 21:14:12 +0200 [thread overview]
Message-ID: <87prh7abqz.fsf@iki.fi> (raw)
In-Reply-To: <20090224191002.GF22108@duck.suse.cz> (Jan Kara's message of "Tue\, 24 Feb 2009 20\:10\:02 +0100")
On 2009-02-24 20:10 (+0100), Jan Kara wrote:
> 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.
Maybe this explanation helps:
http://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977
next prev parent reply other threads:[~2009-02-24 19:15 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
2009-02-24 19:14 ` Teemu Likonen [this message]
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=87prh7abqz.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=git@peter.is-a-geek.org \
--cc=git@vger.kernel.org \
--cc=jack@suse.cz \
/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