On Thursday 05 February 2009 21:08, michael wrote: > 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.
Good idea, we can just check out revisions between 1.11 and 1.12, compile, and try them. 1.11.0 is 22499 1.12.0 is 23126 The command to check out specific revision is svn co svn://busybox.net/trunk/busybox -r $rev busybox$rev This might be easier to do than what I described earlier. -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
