I knew there was a `git bisect` command mention in the "git cheat sheet" we used for the JUG talk on Git in September 2008, but I didn't realize it would do what you were looking for! That's cool.
On Tue, Jul 28, 2009 at 10:02 PM, William H. Mitchell < wh...@mitchellsoftwareengineering.com> wrote: > About 18 months ago I posted this: > > Every once in a while I encounter a situation where a code change or a >> library change breaks something in a system but the problem isn't noticed >> until long after the critical change. >> >> I've never gotten up the steam to do it but I've often thought it would be >> interesting to cook up a simple tool that would repeatedly checkout, build, >> and test, using a binary search to zero in on a transition from working to >> broken. >> >> Does anybody know of an existing tool of that sort? >> > > I got no good answers then but at NFJS this last weekend I learned of such > a tool: git bisect! > > Needless to say, with conversion tools you can easily convert a CVS or > Subversion repo to git, and then use git bisect on it. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jug-discussion-unsubscr...@tucson-jug.org > For additional commands, e-mail: jug-discussion-h...@tucson-jug.org > >
