On Mon, Aug 24, 2009 at 6:22 AM, Sanjiv Gupta<sanjiv.gupta@xxxxxxxxxxxxx> wrote: > Excellent description. Thanks for that. I want to merge commits one by one > because I want to run a regression suite on each commit and therefore know > if any one is causing failures. Hi Sanjiv, 'git bisect' is an even better way to do this, in my experience. I wrote a program (http://github.com/apenwarr/gitbuilder/) that automatically runs regression tests against all the new versions on all the new branches. It then publishes the results on a web page and via RSS. gitbuilder does take a shortcut: if commit x passes and commit x+10 passes, it doesn't bother to test commit x+1..9. However, if x+10 fails, it bisects automatically to find the first commit that caused a failure. You could disable this shortcut easily enough, however. Have fun, Avery -- 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