summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: cd747dc)
raw | patch | inline | side by side (parent: cd747dc)
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>
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 |
index f74354f0fe1c4eb68a9d3828a7df732b5248cf29..e5862b9dbbbd69fcd57e8ec85fb0b08f5bf221d0 100644 (file)
# 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
$ 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: