{"thread":{"id":"12782","subject":"[PATCH] Documentation: reworded git-bisect.txt to be less kernel specific.","startedAt":"2008-03-20T23:25:30Z","lastAt":"2008-03-20T23:25:30Z","messageCount":1,"participants":["Rhodes, Kate"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"72542","messageId":"22FFC8CF-A7A3-4AAF-9707-ACA1AC101BDF@gmail.com","threadId":"12782","inReplyTo":null,"subject":"[PATCH] Documentation: reworded git-bisect.txt to be less kernel specific.","fromName":"Rhodes, Kate","fromEmail":"masukomi@gmail.com","sentAt":"2008-03-20T23:25:30Z","receivedAt":"2008-03-20T23:25:30Z","isPatch":true,"sender":{"key":"masukomi@gmail.com","avatar":null},"body":"* Minor modifications to make examples more generically applicable,\nmention the skip option earlier, and be slightly more explicit,\nto aid foreign speakers.\n---\n  Documentation/git-bisect.txt |   14 +++++++-------\n  1 files changed, 7 insertions(+), 7 deletions(-)\n\n\nPatch is attached so that Mail.app won't mangle it.\n\n-masukomi\n\n\n\nFrom 0be29c0f4284995cad6b47ce55d279be00d8ea37 Mon Sep 17 00:00:00 2001\nFrom: Kate Rhodes <masukomi@gmail.com>\nDate: Thu, 20 Mar 2008 19:16:29 -0400\nSubject: [PATCH] Documentation: reworded git-bisect.txt to be less kernel specific.\n\n* Minor modifications to make examples more generically applicable,\nmention the skip option earlier, and be slightly more explicit,\nto aid foreign speakers.\n---\n Documentation/git-bisect.txt |   14 +++++++-------\n 1 files changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\nindex 96585ae..940914c 100644\n--- a/Documentation/git-bisect.txt\n+++ b/Documentation/git-bisect.txt\n@@ -48,9 +48,9 @@ the revision tree and say something like:\n Bisecting: 675 revisions left to test after this\n ------------------------------------------------\n \n-and check out the state in the middle. Now, compile that kernel, and\n-boot it. Now, let's say that this booted kernel works fine, then just\n-do\n+and check out the state in the middle. Then, test for the presence\n+of your bug. If you've found a version where the bug isn't \n+present you can just do \n \n ------------------------------------------------\n $ git bisect good\t\t\t# this one is good\n@@ -62,12 +62,12 @@ which will now say\n Bisecting: 337 revisions left to test after this\n ------------------------------------------------\n \n-and you continue along, compiling that one, testing it, and depending\n-on whether it is good or bad, you say \"git bisect good\" or \"git bisect\n-bad\", and ask for the next bisection.\n+and you continue along, testing each checkout it makes, and depending\n+on whether it is good or bad, you say \"git bisect good\", \"git bisect\n+bad\", or \"git bisect skip\" ( see below ) and ask for the next bisection.\n \n Until you have no more left, and you'll have been left with the first\n-bad kernel rev in \"refs/bisect/bad\".\n+bad rev in \"refs/bisect/bad\".\n \n Bisect reset\n ~~~~~~~~~~~~\n-- \n1.5.4.1.1278.gc75be\n\n\n\n\n"}]}