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

Re: is smarter bisect possible?

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Sep 25, 2009, 07:59 UTC
Message-ID
<4ABC7865.7010705@viscovery.net>
In-Reply-To
<h9hrv3$cao$1@ger.gmane.org>
Arkadiusz Miśkiewicz schrieb:
Show 13 quoted lines
> I have such problem. Linus kernel tree merged some feature 
> (94e0fb086fc5663c38bbc0fe86d698be8314f82f) that was developed in .31rc9 era.
> 
> Current Linus kernel tree with that feature merged shows some regression. 
> Tree just before that merge doesn't show regression.
> 
> Now if I start to bisect just that feature (good 
> b7f21bb2e23b4fec16b448a34889f467465be659, bad 
> 94e0fb086fc5663c38bbc0fe86d698be8314f82f) then git gets me whole tree back 
> to .31rc9 era which... doesn't show any problems.
> 
> This means that only combined current Linus tree and that feature shows a 
> problem.
Try this:
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#bisect-merges
-- Hannes
Previous: Arkadiusz Miśkiewicz
Message 2 of 2 in “is smarter bisect possible?”
  1. Arkadiusz MiśkiewiczSep 25, 2009
  2. Johannes SixtSep 25, 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.