On Tue, 14 Apr 2020 at 10:33, Gene Heskett <[email protected]> wrote:
> How, since even the newer, bad code runs thru runtests w/o any problems, Bisect does not care how you test. But it is probably easiest to run it on the machine that is showing the problem. > Can someone suggest a starting branch that ideally would start the bisect > say at 2 weeks prior to the beginning of the 2.8 merge, just to verify > it did work then? 2.8 merges in to master rather regularly, but 2 weeks ago would be 7bfebcb23a643c084fc39f1d3bfca9a29c64ae6c (just from browsing https://github.com/LinuxCNC/linuxcnc/commits/master) git checkout 7bfebcb23a643c084fc39f1d3bfca9a29c64ae6c Will take you back in time 2 weeks. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
