On 12/14/06, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
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. n0dalus. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html