Give an example on how to bisect when older revisions need a hotfix to build, run or test. Triggered by the binutils/kernel issue at http://thread.gmane.org/gmane.comp.gnu.binutils/52601/focus=1112779 Signed-off-by: Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> --- Maybe this doc fix would do. Just tag the hotfix and tell people to cherry-pick it like this. I don't think "git bisect --with-fix=hotfix" would be much simpler. (culling kernel list from cc - don't apply this to the wrong tree :) Documentation/git-bisect.txt | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt index c39d957..25acf26 100644 --- a/Documentation/git-bisect.txt +++ b/Documentation/git-bisect.txt @@ -322,6 +322,17 @@ $ git bisect run sh -c "make || exit 125; ~/check_test_case.sh" + Does the same as the previous example, but on a single line. +* Bisect with compatibility hotfix: ++ +------------ +$ git bisect start HEAD HEAD~10 -- # culprit is among the last 10 +$ git bisect run sh -c "git cherry-pick -n hotfix || exit 125; make || exit 125; ~/check_test_case.sh" +------------ ++ +Does the same as the previous example, but applies an additional patch +before building. This is useful when your build or test environment changed so +that older revisions may need a fix which newer ones have already. + Author ------ Written by Linus Torvalds <torvalds@xxxxxxxx> -- 1.7.4.1.404.g62d316 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html