diff options
authorMichael J Gruber <>2011-03-15 21:24:56 (GMT)
committerJunio C Hamano <>2011-03-15 23:06:08 (GMT)
commite235b9168d8df2bc00ca2c77703ce1a98935c906 (patch)
parent9d79b7e95d9acf07ff1479f41faa860503ce280e (diff)
git-bisect.txt: example for bisecting with hot-fix
Give an example on how to bisect when older revisions need a hot-fix to build, run or test. Triggered by the binutils/kernel issue at Signed-off-by: Michael J Gruber <> Signed-off-by: Junio C Hamano <>
1 files changed, 33 insertions, 0 deletions
diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt
index 47e8b1e..989e223 100644
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@@ -294,6 +294,39 @@ It is safer if both "" and "" are
outside the repository to prevent interactions between the bisect,
make and test processes and the scripts.
+* Automatically bisect with temporary modifications (hot-fix):
+$ cat ~/
+# tweak the working tree by merging the hot-fix branch
+# and then attempt a build
+if git merge --no-commit hot-fix &&
+ make
+ # run project specific test and report its status
+ ~/
+ status=$?
+ # tell the caller this is untestable
+ status=125
+# undo the tweak to allow clean flipping to the next commit
+git reset --hard
+# return control
+exit $status
+This applies modifications from a hot-fix branch before each test run,
+e.g. in case your build or test environment changed so that older
+revisions may need a fix which newer ones have already. (Make sure the
+hot-fix branch is based off a commit which is contained in all revisions
+which you are bisecting, so that the merge does not pull in too much, or
+use `git cherry-pick` instead of `git merge`.)
* Automatically bisect a broken test case: