{"thread":{"id":"16555","subject":"[PATCH 2/2 v2] Documentation: describe how to \"bisect skip\" a range of commits","startedAt":"2008-12-02T13:53:51Z","lastAt":"2008-12-03T02:17:46Z","messageCount":2,"participants":["Christian Couder","Junio C Hamano"],"isPatch":true,"patchVersion":2,"patchTotal":2},"messages":[{"id":"96942","messageId":"20081202145351.24d1a1fb.chriscool@tuxfamily.org","threadId":"16555","inReplyTo":null,"subject":"[PATCH 2/2 v2] Documentation: describe how to \"bisect skip\" a range of commits","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2008-12-02T13:53:51Z","receivedAt":"2008-12-02T13:53:51Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Signed-off-by: Christian Couder <chriscool@tuxfamily.org>\n---\n Documentation/git-bisect.txt |   21 ++++++++++++++++++++-\n git-bisect.sh                |    2 +-\n 2 files changed, 21 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\nindex 39034ec..147ea38 100644\n--- a/Documentation/git-bisect.txt\n+++ b/Documentation/git-bisect.txt\n@@ -19,7 +19,7 @@ on the subcommand:\n  git bisect start [<bad> [<good>...]] [--] [<paths>...]\n  git bisect bad [<rev>]\n  git bisect good [<rev>...]\n- git bisect skip [<rev>...]\n+ git bisect skip [(<rev>|<range>)...]\n  git bisect reset [<branch>]\n  git bisect visualize\n  git bisect replay <logfile>\n@@ -164,6 +164,25 @@ But computing the commit to test may be slower afterwards and git may\n eventually not be able to tell the first bad among a bad and one or\n more \"skip\"ped commits.\n \n+You can even skip a range of commits, instead of just one commit,\n+using the \"'<commit1>'..'<commit2>'\" notation. For example:\n+\n+------------\n+$ git bisect skip v2.5..v2.6\n+------------\n+\n+would mean that no commit between `v2.5` excluded and `v2.6` included\n+can be tested.\n+\n+Note that if you want to also skip the first commit of a range you can\n+use something like:\n+\n+------------\n+$ git bisect skip v2.5 v2.5..v2.6\n+------------\n+\n+and the commit pointed to by `v2.5` will be skipped too.\n+\n Cutting down bisection by giving more parameters to bisect start\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \ndiff --git a/git-bisect.sh b/git-bisect.sh\nindex ddbdba8..17a35f6 100755\n--- a/git-bisect.sh\n+++ b/git-bisect.sh\n@@ -9,7 +9,7 @@ git bisect bad [<rev>]\n         mark <rev> a known-bad revision.\n git bisect good [<rev>...]\n         mark <rev>... known-good revisions.\n-git bisect skip [<rev>...]\n+git bisect skip [(<rev>|<range>)...]\n         mark <rev>... untestable revisions.\n git bisect next\n         find next bisection to test and check it out.\n-- \n1.6.0.4.838.g4ea49\n"},{"id":"97006","messageId":"7vfxl6j92t.fsf@gitster.siamese.dyndns.org","threadId":"16555","inReplyTo":"20081202145351.24d1a1fb.chriscool@tuxfamily.org","subject":"Re: [PATCH 2/2 v2] Documentation: describe how to \"bisect skip\" a range of commits","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-12-03T02:17:46Z","receivedAt":"2008-12-03T02:17:46Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thanks.\n"}]}