Greetings all; git-bisect has more options than a new car.
How, since even the newer, bad code runs thru runtests w/o any problems, I need to setup a git bisect start slightly before the 2.8 merge started, then bring it up to head=master & bad. 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? Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene> _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
