Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
Documentation: Remove spurious uses of "you" in git-bisect.txt.
author
David J. Mellor
<dmellor@whistlingcat.com>
Thu, 26 Mar 2009 03:44:44 +0000
(20:44 -0700)
committer
Junio C Hamano
<gitster@pobox.com>
Thu, 26 Mar 2009 03:47:29 +0000
(20:47 -0700)
These were added by accident in
a42dea3
.
This patch also rewords the description of how ranges of commits can be
skipped.
Signed-off-by: David J. Mellor <dmellor@whistlingcat.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-bisect.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
cd747dc
)
diff --git
a/Documentation/git-bisect.txt
b/Documentation/git-bisect.txt
index f74354f0fe1c4eb68a9d3828a7df732b5248cf29..e5862b9dbbbd69fcd57e8ec85fb0b08f5bf221d0 100644
(file)
--- a/
Documentation/git-bisect.txt
+++ b/
Documentation/git-bisect.txt
@@
-151,7
+151,7
@@
$ git reset --hard HEAD~3 # try 3 revisions before what
# was suggested
------------
# was suggested
------------
-Then
you compile and test the chosen revision. Afterwards you
mark
+Then
compile and test the chosen revision, and afterwards
mark
the revision as good or bad in the usual manner.
Bisect skip
the revision as good or bad in the usual manner.
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
------------
-This tells the bisect process that no commit
between `v2.5` excluded
and
-
`v2.6` included
should be tested.
+This tells the bisect process that no commit
after `v2.5`, up to
and
+
including `v2.6`,
should be tested.
Note that if you also want to skip the first commit of the range you
would issue the command:
Note that if you also want to skip the first commit of the range you
would issue the command: