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

Re: bisect help

From
Junio C Hamano <junkio@cox.net>
Date
Jun 27, 2006, 22:41 UTC
Message-ID
<7vu0666x2r.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060627220421.GA7234@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> Since 'test' is a throwaway branch anyway, might it not make sense to
> clone master to test and then rebase satadev onto it? Thus you would end
> up with the linear history:
>   o---o---o---o---o---o---o test (satadev')
>   |           |
> 2.6.17      master
>
> You know that master works and satadev' doesn't, and the bisection is
> simple. After you find that bug, you can throw away the test branch.

I've considered suggesting it before looking at what is in satadev. It is merged up in the Linus head right now, so you are talking about really _huge_ changes that are not yours and with a lot of merges.

It usually is much easier to rebase your own code than other's.

BTW, I really hate MUA's that does Mail-Followup-To to somebody else. This message for example would not help Martin more than it would help you, but your MUA somehow redirected it to him.

Previous: Jeff KingNext: Martin Hicks
Message 4 of 5 in “bisect help”
  1. Martin HicksJun 27, 2006
  2. Junio C HamanoJun 27, 2006
  3. Jeff KingJun 27, 2006
  4. Junio C HamanoJun 27, 2006
  5. Martin HicksJun 27, 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.