{"thread":{"id":"14771","subject":"[PATCH] documentation: user-manual: update \"using-bisect\" section","startedAt":"2008-07-31T03:22:40Z","lastAt":"2008-07-31T05:59:42Z","messageCount":2,"participants":["Christian Couder","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"85721","messageId":"20080731052240.23455ddb.chriscool@tuxfamily.org","threadId":"14771","inReplyTo":null,"subject":"[PATCH] documentation: user-manual: update \"using-bisect\" section","fromName":"Christian Couder","fromEmail":"chriscool@tuxfamily.org","sentAt":"2008-07-31T03:22:40Z","receivedAt":"2008-07-31T03:22:40Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Since version 1.5.6 \"git bisect\" doesn't use a \"bisect\" branch any\nmore, but the user manual had not been updated to reflect this.\n\nSo this patch does that and while at it also adds a few words about\n\"git bisect skip\" and points user to the \"git bisect\" man page for\nmore information.\n\nSigned-off-by: Christian Couder <chriscool@tuxfamily.org>\n---\n Documentation/user-manual.txt |   27 +++++++++++++++++++++------\n 1 files changed, 21 insertions(+), 6 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex c5641af..50bf85f 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -479,10 +479,10 @@ Bisecting: 3537 revisions left to test after this\n -------------------------------------------------\n \n If you run \"git branch\" at this point, you'll see that git has\n-temporarily moved you to a new branch named \"bisect\".  This branch\n-points to a commit (with commit id 65934...) that is reachable from\n-\"master\" but not from v2.6.18.  Compile and test it, and see whether\n-it crashes.  Assume it does crash.  Then:\n+temporarily moved you in \"(no branch)\". HEAD is now detached from any\n+branch and points directly to a commit (with commit id 65934...) that\n+is reachable from \"master\" but not from v2.6.18. Compile and test it,\n+and see whether it crashes. Assume it does crash. Then:\n \n -------------------------------------------------\n $ git bisect bad\n@@ -504,8 +504,7 @@ report with the commit id.  Finally, run\n $ git bisect reset\n -------------------------------------------------\n \n-to return you to the branch you were on before and delete the\n-temporary \"bisect\" branch.\n+to return you to the branch you were on before.\n \n Note that the version which git-bisect checks out for you at each\n point is just a suggestion, and you're free to try a different\n@@ -528,6 +527,22 @@ $ git reset --hard fb47ddb2db...\n then test, run \"bisect good\" or \"bisect bad\" as appropriate, and\n continue.\n \n+Instead of \"git bisect visualize\" and then \"git reset --hard\n+fb47ddb2db...\", you might just want to tell git that you want to skip\n+the current commit:\n+\n+-------------------------------------------------\n+$ git bisect skip\n+-------------------------------------------------\n+\n+In this case, though, git may not eventually be able to tell the first\n+bad one between some first skipped commits and a latter bad commit.\n+\n+There are also ways to automate the bisecting process if you have a\n+test script that can tell a good from a bad commit. See\n+linkgit:git-bisect[1] for more information about this and other \"git\n+bisect\" features.\n+\n [[naming-commits]]\n Naming commits\n --------------\n-- \n1.6.0.rc0.42.g186458.dirty\n"},{"id":"85730","messageId":"7vod4e386p.fsf@gitster.siamese.dyndns.org","threadId":"14771","inReplyTo":"20080731052240.23455ddb.chriscool@tuxfamily.org","subject":"Re: [PATCH] documentation: user-manual: update \"using-bisect\" section","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-07-31T05:59:42Z","receivedAt":"2008-07-31T05:59:42Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thanks, applied.\n"}]}