On Tuesday, March 20, 2007 at 00:33:41 (-0400) Shawn O. Pearce writes: >This is a simple but powerful continuous integration build system >for Git. ... This looks quite useful. Thanks for sharing your "hack". For some reason, this got me to thinking about automated bisection. The way I understand bisection to work is that you mark starting and ending points (good vs. bad), then you do some work, and tell git if the current point is good or bad, continuing on until you find the first baddie. This is a very thoughtful piece of software. However, would it be possible to automate this, say by designating a script to run that would automatically return the "good" vs. "bad", allowing you to run off to lunch (or more) and let it determine the first bad point? Something like this: % git bisect start % git bisect bad % git bisect good v2.6.13-rc2 % git bisect run my_script I suppose one could just write a wrapper script, but perhaps this would be convenient enough... Bill - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html