{"thread":{"id":"7379","subject":"[PATCH 3/5] Documentation: bisect: reformat more paragraphs.","startedAt":"2007-03-24T05:31:49Z","lastAt":"2007-03-24T05:31:49Z","messageCount":1,"participants":["Christian Couder"],"isPatch":true,"patchVersion":1,"patchTotal":5},"messages":[{"id":"37859","messageId":"20070324063149.56655ec8.chriscool@tuxfamily.org","threadId":"7379","inReplyTo":"20070324061307.127b2cbf.chriscool@tuxfamily.org","subject":"[PATCH 3/5] Documentation: bisect: reformat more paragraphs.","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2007-03-24T05:31:49Z","receivedAt":"2007-03-24T05:31:49Z","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 |   73 ++++++++++++++++++++++-------------------\n 1 files changed, 39 insertions(+), 34 deletions(-)\n\ndiff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt\nindex 4bd468e..0bf8a08 100644\n--- a/Documentation/git-bisect.txt\n+++ b/Documentation/git-bisect.txt\n@@ -12,8 +12,8 @@ SYNOPSIS\n \n DESCRIPTION\n -----------\n-The command takes various subcommands, and different options\n-depending on the subcommand:\n+The command takes various subcommands, and different options depending\n+on the subcommand:\n \n  git bisect start [<paths>...]\n  git bisect bad <rev>\n@@ -24,10 +24,9 @@ depending on the subcommand:\n  git bisect log\n  git bisect run <cmd>...\n \n-This command uses 'git-rev-list --bisect' option to help drive\n-the binary search process to find which change introduced a bug,\n-given an old \"good\" commit object name and a later \"bad\" commit\n-object name.\n+This command uses 'git-rev-list --bisect' option to help drive the\n+binary search process to find which change introduced a bug, given an\n+old \"good\" commit object name and a later \"bad\" commit object name.\n \n The way you use it is:\n \n@@ -38,15 +37,16 @@ $ git bisect good v2.6.13-rc2\t\t# v2.6.13-rc2 was the last version\n \t\t\t\t\t# tested that was good\n ------------------------------------------------\n \n-When you give at least one bad and one good versions, it will\n-bisect the revision tree and say something like:\n+When you give at least one bad and one good versions, it will bisect\n+the revision tree and say something like:\n \n ------------------------------------------------\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 boot\n-it. Now, let's say that this booted kernel works fine, then just do\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 \n ------------------------------------------------\n $ git bisect good\t\t\t# this one is good\n@@ -58,12 +58,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 on\n-whether it is good or bad, you say \"git bisect good\" or \"git bisect bad\",\n-and ask for the next bisection.\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 \n-Until you have no more left, and you'll have been left with the first bad\n-kernel rev in \"refs/bisect/bad\".\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 \n Oh, and then after you want to reset to the original head, do a\n \n@@ -71,10 +71,10 @@ Oh, and then after you want to reset to the original head, do a\n $ git bisect reset\n ------------------------------------------------\n \n-to get back to the master branch, instead of being in one of the bisection\n-branches (\"git bisect start\" will do that for you too, actually: it will\n-reset the bisection state, and before it does that it checks that you're\n-not using some old bisection branch).\n+to get back to the master branch, instead of being in one of the\n+bisection branches (\"git bisect start\" will do that for you too,\n+actually: it will reset the bisection state, and before it does that\n+it checks that you're not using some old bisection branch).\n \n During the bisection process, you can say\n \n@@ -84,9 +84,14 @@ $ git bisect visualize\n \n to see the currently remaining suspects in `gitk`.\n \n-The good/bad input is logged, and `git bisect\n-log` shows what you have done so far.  You can truncate its\n-output somewhere and save it in a file, and run\n+The good/bad input is logged, and \n+\n+------------\n+$ git bisect log\n+------------\n+\n+shows what you have done so far. You can truncate its output somewhere\n+and save it in a file, and run\n \n ------------\n $ git bisect replay that-file\n@@ -95,12 +100,13 @@ $ git bisect replay that-file\n if you find later you made a mistake telling good/bad about a\n revision.\n \n-If in a middle of bisect session, you know what the bisect\n-suggested to try next is not a good one to test (e.g. the change\n-the commit introduces is known not to work in your environment\n-and you know it does not have anything to do with the bug you\n-are chasing), you may want to find a near-by commit and try that\n-instead.  It goes something like this:\n+If in a middle of bisect session, you know what the bisect suggested\n+to try next is not a good one to test (e.g. the change the commit\n+introduces is known not to work in your environment and you know it\n+does not have anything to do with the bug you are chasing), you may\n+want to find a near-by commit and try that instead.\n+\n+It goes something like this:\n \n ------------\n $ git bisect good/bad\t\t\t# previous round was good/bad.\n@@ -110,13 +116,12 @@ $ git reset --hard HEAD~3\t\t# try 3 revs before what\n \t\t\t\t\t# was suggested\n ------------\n \n-Then compile and test the one you chose to try.  After that,\n-tell bisect what the result was as usual.\n+Then compile and test the one you chose to try. After that, tell\n+bisect what the result was as usual.\n \n-You can further cut down the number of trials if you know what\n-part of the tree is involved in the problem you are tracking\n-down, by giving paths parameters when you say `bisect start`,\n-like this:\n+You can further cut down the number of trials if you know what part of\n+the tree is involved in the problem you are tracking down, by giving\n+paths parameters when you say `bisect start`, like this:\n \n ------------\n $ git bisect start arch/i386 include/asm-i386\n-- \n1.5.1.rc1.14.ge96a-dirty\n"}]}