kernel
/
git
mirror of https://git.kernel.org/pub/scm/git/git.git
1
0
Fork 0
Code Releases Activity

Documentation: remove some uses of the passive voice in git-bisect.txt 

Signed-off-by: David J. Mellor <dmellor@whistlingcat.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
David J. Mellor 2009-03-22 20:11:10 -07:00 committed by Junio C Hamano
parent 4306bcb4e1
commit a42dea3281
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
Documentation/git-bisect.txt
View File

@ -81,7 +81,7 @@ will have been left with the first bad kernel revision in "refs/bisect/bad".
Bisect reset Bisect reset
~~~~~~~~~~~~ ~~~~~~~~~~~~


To return to the original head after a bisect session, you issue the To return to the original head after a bisect session, issue the
following command: following command:


------------------------------------------------ ------------------------------------------------
@ -95,8 +95,8 @@ the bisection state).
Bisect visualize Bisect visualize
~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~


To see the currently remaining suspects in 'gitk', the following command To see the currently remaining suspects in 'gitk', issue the following
is issued during the bisection process: command during the bisection process:


------------ ------------
$ git bisect visualize $ git bisect visualize
@ -115,7 +115,7 @@ $ git bisect view --stat
Bisect log and bisect replay Bisect log and bisect replay
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~


After having marked revisions as good or bad, you issue the following After having marked revisions as good or bad, issue the following
command to show what has been done so far: command to show what has been done so far:


------------ ------------
@ -135,7 +135,7 @@ $ git bisect replay that-file
Avoiding testing a commit Avoiding testing a commit
~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~


If in the middle of a bisect session, you know that the next suggested If, in the middle of a bisect session, you know that the next suggested
revision is not a good one to test (e.g. the change the commit revision is not a good one to test (e.g. the change the commit
introduces is known not to work in your environment and you know it introduces is known not to work in your environment and you know it
does not have anything to do with the bug you are chasing), you may does not have anything to do with the bug you are chasing), you may
@ -151,8 +151,8 @@ $ git reset --hard HEAD~3 # try 3 revisions before what
# was suggested # was suggested
------------ ------------


Then compile and test the chosen revision. Afterwards the revision Then you compile and test the chosen revision. Afterwards you mark
is marked as good or bad in the usual manner. the revision as good or bad in the usual manner.


Bisect skip Bisect skip
~~~~~~~~~~~~ ~~~~~~~~~~~~
@ -175,8 +175,8 @@ using the "'<commit1>'..'<commit2>'" notation. For example:
$ git bisect skip v2.5..v2.6 $ git bisect skip v2.5..v2.6
------------ ------------


The effect of this would be that no commit between `v2.5` excluded and This tells the bisect process that no commit between `v2.5` excluded and
`v2.6` included could be tested. `v2.6` included should be tested.


Note that if you also want to skip the first commit of the range you Note that if you also want to skip the first commit of the range you
would issue the command: would issue the command:
@ -185,8 +185,8 @@ would issue the command:
$ git bisect skip v2.5 v2.5..v2.6 $ git bisect skip v2.5 v2.5..v2.6
------------ ------------


This would cause the commits between `v2.5` included and `v2.6` included This tells the bisect process that the commits between `v2.5` included
to be skipped. and `v2.6` included should be skipped.




Cutting down bisection by giving more parameters to bisect start Cutting down bisection by giving more parameters to bisect start