On Thu, 5 Feb 2009, Denys Vlasenko wrote: > These are good news! Figuring out where ash broke would be worse. <long saga about bisecting the changes snipped> > I'm afraid starting from there you will need to > split these three patches into smaller pieces > and continue bisecting the bug. > > It's long and not interesting work, but it's not requiring > you to actually think much, it's mechanic, and in the end, > it's bound to success - you will find a small change which > causes it.
This sounds awfully like `git bisect` without git. A slightly easier approach might be to use `git svn clone` to read the entire busybox svn history into git (it's a bit demanding on the busybox server, but it works fine, I've done it) ... and then you can actually use git bisect -- so long as the two releases are in the svn history. Just a thought. _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
