On Thu, Feb 13, 2014 at 6:34 PM, Liviu Andronic <landronim...@gmail.com> wrote: > 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.
Depends. If you want to be safe but take a longer time, just do a git clean. You might be safe with 'make clean' most of the time, but I'm really not sure. Someone else would know better than I. Scott
