Reformatted excerpts from Ben Walton's message of 2009-04-30: > git-bisect to the rescue? Anyone experiencing this and comfortable > with git that wants to track down where the problem was introduced? > It may take a little while, unless the problem can be recreated at > will, but the bisect tool is awesome for situations like this.
If the educated guesses fall through, then we'll punish Steve for his insulin by making him binary search through all commits since 0.7. -- William <[email protected]> _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
