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

Re: Problem with git bisect in git-1.6.3.3

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jul 9, 2009, 06:39 UTC
Message-ID
<4A5590A3.8070404@viscovery.net>
In-Reply-To
<c6b1100b0907082242y7b348b13m8a4607c96b1d164b@mail.gmail.com>
Chris Clayton schrieb:
> git bisect start
> # good: [07a2039b8eb0af4ff464efd3dfd95de5c02648c6] Linux 2.6.30
> git bisect good 07a2039b8eb0af4ff464efd3dfd95de5c02648c6
> # bad: [8e4a718ff38d8539938ec3421935904c27e00c39] Linux 2.6.31-rc2
...
Show 8 quoted lines
> but, from Makefile, it appears the last "bad" has placed me at a
> change earlier than 2.6.30:
> 
> [chris:~/kernel/linux-2.6]$ head Makefile
> VERSION = 2
> PATCHLEVEL = 6
> SUBLEVEL = 30
> EXTRAVERSION = -rc6
...
> I'm not an experienced git user, so it may be that I have made an
> error or false assumption.
Not an error, but false assumptions:
http://thread.gmane.org/gmane.comp.version-control.git/99967/focus=99977

Just continue bisecting. If you can't test the version that bisect warps you to because the feature where the bug happens is not present, mark that revision as "good".

-- Hannes
Previous: Chris ClaytonNext: Chris Clayton
Message 2 of 4 in “Problem with git bisect in git-1.6.3.3”
  1. Chris ClaytonJul 9, 2009
  2. Johannes SixtJul 9, 2009
  3. Chris ClaytonJul 9, 2009
  4. Christian CouderJul 10, 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.