this is wrt to a question which came up yesterday on #emc-devel while cradek reviewed my candidate branch for revised toolchange support
I had rebased some commits interactively and broken sequencing while doing so such that HEAD, but not each commit would build; cradek spotted this the question came up wether there's an automatic way to check a branch for each commit being buildable. Well, there is: see http://dustin.github.com/2010/03/28/git-test-sequence.html , and the code at https://github.com/dustin/bindir/blob/master/git-test-sequence use as follows (in this case testing every commit from origin/master to HEAD): $ git-test-sequence origin/master.. '(cd src;make)' This will either report 'All's well' or 'Broke on <commit>' (after running a loooong time). here's the output reporting my goof: emc/task/iotaskintf.cc: In function ‘int emcIoAbort(int)’: emc/task/iotaskintf.cc:295: error: ‘class EMC_TOOL_ABORT’ has no member named ‘reason’ emc/task/iotaskintf.cc:300: error: ‘emcAbortCleanup’ was not declared in this scope make: *** [objects/emc/task/iotaskintf.o] Error 1 make: Leaving directory `/home/mah/emc2-dev/src' Broke on e0d97a110a5ab7a039d592b2874899f2c6a9f7ed Switched to branch 'iocontrolv2-toolchange-gcode-osub-candidate' Deleted branch test_seq_13248 (was e0d97a1). ----- -mah ps: I had to fix . "$(git --exec-path)/git-sh-setup" #. git-sh-setup ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers