From: Rhodes, Kate Date: Thu, 20 Mar 2008 23:25:30 GMT Subject: [PATCH] Documentation: reworded git-bisect.txt to be less kernel specific. Message-ID: <22FFC8CF-A7A3-4AAF-9707-ACA1AC101BDF@gmail.com> * Minor modifications to make examples more generically applicable, mention the skip option earlier, and be slightly more explicit, to aid foreign speakers. --- Documentation/git-bisect.txt | 14 +++++++------- 1 files changed, 7 insertions(+), 7 deletions(-) Patch is attached so that Mail.app won't mangle it. -masukomi From 0be29c0f4284995cad6b47ce55d279be00d8ea37 Mon Sep 17 00:00:00 2001 From: Kate Rhodes Date: Thu, 20 Mar 2008 19:16:29 -0400 Subject: [PATCH] Documentation: reworded git-bisect.txt to be less kernel specific. * Minor modifications to make examples more generically applicable, mention the skip option earlier, and be slightly more explicit, to aid foreign speakers. --- Documentation/git-bisect.txt | 14 +++++++------- 1 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt index 96585ae..940914c 100644 --- a/Documentation/git-bisect.txt +++ b/Documentation/git-bisect.txt @@ -48,9 +48,9 @@ the revision tree and say something like: Bisecting: 675 revisions left to test after this ------------------------------------------------ -and check out the state in the middle. Now, compile that kernel, and -boot it. Now, let's say that this booted kernel works fine, then just -do +and check out the state in the middle. Then, test for the presence +of your bug. If you've found a version where the bug isn't +present you can just do ------------------------------------------------ $ git bisect good # this one is good @@ -62,12 +62,12 @@ which will now say Bisecting: 337 revisions left to test after this ------------------------------------------------ -and you continue along, compiling that one, testing it, and depending -on whether it is good or bad, you say "git bisect good" or "git bisect -bad", and ask for the next bisection. +and you continue along, testing each checkout it makes, and depending +on whether it is good or bad, you say "git bisect good", "git bisect +bad", or "git bisect skip" ( see below ) and ask for the next bisection. Until you have no more left, and you'll have been left with the first -bad kernel rev in "refs/bisect/bad". +bad rev in "refs/bisect/bad". Bisect reset ~~~~~~~~~~~~ -- 1.5.4.1.1278.gc75be