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

Re: Using git-bisect to find more than one breakage

From
Nn0dalus <n0dalus+redhat@gmail.com>
Date
Dec 13, 2006, 15:06 UTC
Message-ID
<6280325c0612130706keb86890n1395ec765a140d60@mail.gmail.com>
In-Reply-To
<20061213143404.GA24132@fieldses.org>
On 12/14/06, J. Bruce Fields <bfields@fieldses.org> wrote:
Show 11 quoted lines
> On Tue, Dec 12, 2006 at 03:04:29PM +1030, n0dalus wrote:
> >
> > I am thinking for now I will just use git-bisect between the bad
> > commit and master, and apply my changes to every bisection.
>
> Yes, that's the way to do it.
>
> The git-rebase command is intended for rebasing small pieces of purely
> linear history; I don't believe it will work well (at all?) to rebase a
> large chunk of kernel history.
>
Yeah, I figured it couldn't deal with all the merges and stuff.

It'd be nice if the man page for git-rebase warned about it's inability to handle lots of complex merges. Or if the git-bisect man page mentioned that the easiest way to find more than one problem is to find and fix the first, then apply that fix to every bisection between that first problem and a known bad version.

Thanks though, now I can stop worrying about why the rebase wasn't working and concentrate on finding the bugs.

Previous: J. Bruce Fields
Message 3 of 3 in “Using git-bisect to find more than one breakage”
  1. n0dalusDec 12, 2006
  2. J. Bruce FieldsDec 13, 2006
  3. n0dalusDec 13, 2006

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.