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>
David J. Mellor committed
Mar 22, 2009 at 20:11 UTC
a42dea3281898b06be687f6763e1a52b898ac2d8
1 file changed
+11
-11
Documentation/git-bisect.txt
+11
-11
@@ -81,7 +81,7 @@ will have been left with the first bad kernel revision in "refs/bisect/bad".
81
Bisect reset
82
~~~~~~~~~~~~
83
84
-To return to the original head after a bisect session, you issue the
84
+To return to the original head after a bisect session, issue the
85
following command:
86
87
------------------------------------------------
@@ -95,8 +95,8 @@ the bisection state).
95
Bisect visualize
96
~~~~~~~~~~~~~~~~
97
98
-To see the currently remaining suspects in 'gitk', the following command
99
-is issued during the bisection process:
98
+To see the currently remaining suspects in 'gitk', issue the following
99
+command during the bisection process:
100
101
------------
102
$ git bisect visualize
@@ -115,7 +115,7 @@ $ git bisect view --stat
115
Bisect log and bisect replay
116
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
117
118
-After having marked revisions as good or bad, you issue the following
118
+After having marked revisions as good or bad, issue the following
119
command to show what has been done so far:
120
121
------------
@@ -135,7 +135,7 @@ $ git bisect replay that-file
135
Avoiding testing a commit
136
~~~~~~~~~~~~~~~~~~~~~~~~~
137
138
-If in the middle of a bisect session, you know that the next suggested
138
+If, in the middle of a bisect session, you know that the next suggested
139
revision is not a good one to test (e.g. the change the commit
140
introduces is known not to work in your environment and you know it
141
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
151
# was suggested
152
------------
153
154
-Then compile and test the chosen revision. Afterwards the revision
155
-is marked as good or bad in the usual manner.
154
+Then you compile and test the chosen revision. Afterwards you mark
155
+the revision as good or bad in the usual manner.
156
157
Bisect skip
158
~~~~~~~~~~~~
@@ -175,8 +175,8 @@ using the "'<commit1>'..'<commit2>'" notation. For example:
175
$ git bisect skip v2.5..v2.6
176
------------
177
178
-The effect of this would be that no commit between `v2.5` excluded and
179
-`v2.6` included could be tested.
178
+This tells the bisect process that no commit between `v2.5` excluded and
179
+`v2.6` included should be tested.
180
181
Note that if you also want to skip the first commit of the range you
182
would issue the command:
@@ -185,8 +185,8 @@ would issue the command:
185
$ git bisect skip v2.5 v2.5..v2.6
186
------------
187
188
-This would cause the commits between `v2.5` included and `v2.6` included
189
-to be skipped.
188
+This tells the bisect process that the commits between `v2.5` included
189
+and `v2.6` included should be skipped.
190
191
192
Cutting down bisection by giving more parameters to bisect start