Liviu Andronic wrote: > The "local changes" are probably as a result of my doing 'make' on the
exactly. you better do "git checkout -f" instead of stashing. this problem will happen only once, next steps won't do unless you do make distclean. > tree. Then I did 'stash' as instructed: > > geek@liv-HP-Compaq-dc7900:~/Build/lyx-trunk/lyx$ git stash > Saved working directory and index state WIP on (no branch): 536a0b4 > Move layout editor zombie to attic. > HEAD is now at 536a0b4 Move layout editor zombie to attic. > geek@liv-HP-Compaq-dc7900:~/Build/lyx-trunk/lyx$ git bisect bad > Bisecting: 994 revisions left to test after this (roughly 10 steps) > [76c5902b4060e0a15b6c23dff273ad6721a9ac69] Parse the picture variant > of \framebox correctly (part of bug #6449) > > But now after 'make' the compilation seems to be taking ages (as a > cold compilation would do). I was expecting that it would only rebuild > the changed bits. Am I missing something? unless you are in last few bisect steps it will usually need to recompile the whole tree, because even cosmetic change in few header files strikes everywhere. > PS Moreover, the compilation failed. What do you do when that happens? > git bisect bad? no. structure of files or makefiles changes coud happen meanwhile. make clean will catch only some cases, make distclean will catch most of them (but you'll need to run autogen and configure again) and it happened few times to me that i need to delete everything except of .git subdir and git checkout -f of that particular revision. p
