git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git bisect goes wild?

From
JKJan Kara <jack@suse.cz>
Date
Feb 24, 2009, 19:28 UTC
Message-ID
<20090224192809.GG22108@duck.suse.cz>
In-Reply-To
<87prh7abqz.fsf@iki.fi>
On Tue 24-02-09 21:14:12, Teemu Likonen wrote:
Show 14 quoted lines
> 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
  OK, thanks for the pointer. I'll trust that the result will be sensible
:).
									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR
Previous: Teemu LikonenNext: Daniel Barkalow
Message 5 of 8 in “git bisect goes wild?”
  1. Jan KaraFeb 24, 2009
  2. Peter HarrisFeb 24, 2009
  3. Jan KaraFeb 24, 2009
  4. Teemu LikonenFeb 24, 2009
  5. Jan KaraFeb 24, 2009
  6. Daniel BarkalowFeb 24, 2009
  7. Jan KaraFeb 24, 2009
  8. Daniel BarkalowFeb 24, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.