On Mar 10, 2009, at 11:00:09, Bryan Henry wrote:
> I'll probably do some regression testing if I get the time and
> hopefully find a build where the crash doesn't occur.
If you do, you can use hg bisect to isolate the specific revision that
caused the crash.
Suppose, for the sake of demonstration, that the crash starts between
1.1 and 1.1.1. You start by marking these as good and bad:
hg bisect -b growl-1.1.1
hg bisect -g growl-1.1
bisect will then update to some revision within this range (probably
the one in the middle—hence “bisection”). You'll test it and give
it a thumbs-up or thumbs-down:
hg bisect -b
hg bisect -g
Eventually, you'll have narrowed it down to the revision that
introduced the problem.
I haven't had an opportunity to use this yet, but it looks awesome. ☺
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en
-~----------~----~----~----~------~----~------~--~---
