Excerpts from William Morgan's message of Thu Apr 30 09:36:22 -0400 2009: > 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.
Bad news. This new branch is also buggy. Time to apply the force of brute. -- Steve Goldman sgold...@tower-research.com T: 212.219.6014 F: 212.219.6007 Tower Research Capital, LLC 377 Broadway, 11th Fl. New York, NY 10013 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
