At the moment I do not use any GUI for git, just the command line version, OS is a Kubuntu 13.10 machine.Code: Select all
# Remove and reconfigure, just to ensure we get clean builds
$ rm -rf build
$ git checkout <revision goes here>
$ mkdir build
$ cd build
$ cmake ../
$ make && sudo make install
# Test out the change ...
$ gqrx
# Rinse and repeat with the next commit
$ cd ../
$ rm -rf build
...
Code: Select all
# Show the git bisect help, which provide some nice details
$ git help bisect
# Initiatie a bisect session
$ git bisect start
# Define the commit we know is bad. HEAD points to the most recent commit, which is 23cfc1dd878d79203fe11a780778263e5b815da6 at this time. You can specifiy 23cfc1dd878d79203fe11a780778263e5b815da6 instead of HEAD, if you'd like/
$ git bisect bad HEAD
# Define the commit we know to be good. Per your investigation, this is e37a34ca3305a06062cc87d4de16d94d4b573acc.
$ git bisect good e37a34ca3305a06062cc87d4de16d94d4b573acc
# Step: Clean and rebuild
# Git will now check out something between the two of these commits. Now let's build and test
$ cd ../
$ rm -rf build
$ mkdir build
$ cd build
$ cmake ../
$ make && sudo make install
# Step: Now test this build...
$ gqrx
# Step: Mark the status of the commit
#If this commit was good, we run:
$ git bisect good
# Otherwise, if this commit failed
$ git bisect bad
# Git will now bisect the remaining set of commits and check out a commit in the middle.
# Go back to "Step: Clean and rebuild" and repeat
# Eventually, you'll land on the guilty commit, and git will show you the commit summary for it.