On Thu, Feb 13, 2014 at 10:35 PM, Scott Kostyshak <skost...@lyx.org> wrote: > On Thu, Feb 13, 2014 at 4:28 PM, Liviu Andronic <landronim...@gmail.com> > wrote: >>> PS Moreover, the compilation failed. What do you do when that happens? >>> git bisect bad? >>> >> It seems: >> git bisect skip > > Yes. I mistakenly omitted that (Jürgen corrected me). > skipping a commit seems like cheating, but git bisect will just have > you check a commit close to there. If the commit you skipped could > possibly be the problem, git bisect will give you more than one commit > as the commits that could have introduced the bug. > Thanks, Scott. One more question: In between two 'git bisect bad' do you need to run 'make clean'? Or just 'make'? So far I couldn't compile any intermediary revision, so I'm starting to wonder if I'm doing something wrong.
Liviu > Scott -- Do you know how to read? http://www.alienetworks.com/srtest.cfm http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader Do you know how to write? http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail
