{"thread":{"id":"18171","subject":"[PATCH] Documentation: More examples for git bisect","startedAt":"2009-03-06T09:37:35Z","lastAt":"2009-03-06T20:08:09Z","messageCount":2,"participants":["John Tapsell","Christian Couder"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"107170","messageId":"1236332255-15712-1-git-send-email-johnflux@gmail.com","threadId":"18171","inReplyTo":null,"subject":"[PATCH] Documentation: More examples for git bisect","fromName":"John Tapsell","fromEmail":"johnflux@gmail.com","sentAt":"2009-03-06T09:37:35Z","receivedAt":"2009-03-06T09:37:35Z","isPatch":true,"sender":{"key":"johnflux@gmail.com","avatar":"https://gravatar.com/avatar/25f70d4c0f96396b84a2e34bcd9bdc233462c7b4be29b5fdca8266fc53f30b0c?d=mp&s=160"},"body":"Including passing parameters to the programs, and running more\ncomplicated checks without requiring a seperate shell script.\n\nSigned-off-by: John Tapsell <johnflux@gmail.com>\n---\n Documentation/git-bisect.txt |   27 ++++++++++++++++++++++++++-\n 1 files changed, 26 insertions(+), 1 deletions(-)\n\ndiff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\nindex 147ea38..7b8cfdd 100644\n--- a/Documentation/git-bisect.txt\n+++ b/Documentation/git-bisect.txt\n@@ -212,7 +212,7 @@ If you have a script that can tell if the current source code is good\n or bad, you can automatically bisect using:\n \n ------------\n-$ git bisect run my_script\n+$ git bisect run my_script arguments\n ------------\n \n Note that the \"run\" script (`my_script` in the above example) should\n@@ -251,6 +251,22 @@ EXAMPLES\n $ git bisect start HEAD v1.2 --      # HEAD is bad, v1.2 is good\n $ git bisect run make                # \"make\" builds the app\n ------------\n++\n+This looks for the first revision that fails to build between HEAD and\n+the tag 'v1.2'.  \n+\n+* Automatically bisect a test failure between origin and HEAD:\n++\n+------------\n+$ git bisect start HEAD origin --    # HEAD is bad, origin is good\n+$ git bisect run make test           # \"make test\" builds and tests\n+------------\n++\n+This looks for the first revision that 'make test' fails for, assuming that\n+you have such a Makefile rule, and that 'make test' also builds the source code.\n+Note however that if the source fails to build, this will be treated as a bad\n+commit.  This may not be what you intend, so the following examples instead\n+treat build failures as commits to skip.\n \n * Automatically bisect a broken test suite:\n +\n@@ -291,6 +307,15 @@ It's safer if both \"test.sh\" and \"check_test_case.sh\" scripts are\n outside the repo to prevent interactions between the bisect, make and\n test processes and the scripts.\n \n+* Automatically bisect a broken test suite, simplified version:\n++\n+------------\n+$ git bisect start HEAD HEAD~10 --   # culprit is among the last 10\n+$ git bisect run sh -c \"make || exit 125; ~/check_test_case.sh\"\n+------------\n++\n+Does the same as the previous example, but on a single line.\n+\n Author\n ------\n Written by Linus Torvalds <torvalds@osdl.org>\n-- \n1.6.2.97.g034f.dirty\n"},{"id":"107238","messageId":"200903062108.09758.chriscool@tuxfamily.org","threadId":"18171","inReplyTo":"1236332255-15712-1-git-send-email-johnflux@gmail.com","subject":"Re: [PATCH] Documentation: More examples for git bisect","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2009-03-06T20:08:09Z","receivedAt":"2009-03-06T20:08:09Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Le vendredi 6 mars 2009, John Tapsell a écrit :\n> Including passing parameters to the programs, and running more\n> complicated checks without requiring a seperate shell script.\n>\n> Signed-off-by: John Tapsell <johnflux@gmail.com>\n> ---\n>  Documentation/git-bisect.txt |   27 ++++++++++++++++++++++++++-\n>  1 files changed, 26 insertions(+), 1 deletions(-)\n>\n> diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\n> index 147ea38..7b8cfdd 100644\n> --- a/Documentation/git-bisect.txt\n> +++ b/Documentation/git-bisect.txt\n> @@ -212,7 +212,7 @@ If you have a script that can tell if the current\n> source code is good or bad, you can automatically bisect using:\n>\n>  ------------\n> -$ git bisect run my_script\n> +$ git bisect run my_script arguments\n>  ------------\n>\n>  Note that the \"run\" script (`my_script` in the above example) should\n> @@ -251,6 +251,22 @@ EXAMPLES\n>  $ git bisect start HEAD v1.2 --      # HEAD is bad, v1.2 is good\n>  $ git bisect run make                # \"make\" builds the app\n>  ------------\n> ++\n> +This looks for the first revision that fails to build between HEAD and\n> +the tag 'v1.2'.\n\nThere are a few trailing spaces in the above line but otherwise the patch \nlooks good to me.\n\nAcked-by: Christian Couder <chriscool@tuxfamily.org>\n\nBy the way, it would be nice if you could put me in CC.\n\nThanks,\nChristian.\n"}]}