"David J. Mellor" <dmellor@xxxxxxxxxxxxxxxx> writes: > 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@xxxxxxxxxxxxxxxx> > --- > Documentation/git-bisect.txt | 6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/git-bisect.txt b/Documentation/git-bisect.txt > index a356a2b..ffc02c7 100644 > --- 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 > ------------ > > -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 > @@ -175,8 +175,8 @@ using the "'<commit1>'..'<commit2>'" notation. For example: > $ 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. Thanks; this part is much easier to read now. These 'excluded/included' have always bothered me. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
