doc: mention rev-list --ancestry-path restrictions

The rev-list documentation doesn't mention that the given
commit must be in the specified commit range, leading
to unexpected results.

Signed-off-by: Kai Koponen <kaikopone@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
index 0d90d5b1549aa2e50647e1a0a6195a2ed301d699..9d5243e0aabe34985f85950b09f27d458173c77e 100644 (file)
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -401,7 +401,8 @@ Default mode::
 
 --ancestry-path[=<commit>]::
        When given a range of commits to display (e.g. 'commit1..commit2'
-       or 'commit2 {caret}commit1'), only display commits in that range
+       or 'commit2 {caret}commit1'), and a commit <commit> in that range,
+       only display commits in that range
        that are ancestors of <commit>, descendants of <commit>, or
        <commit> itself.  If no commit is specified, use 'commit1' (the
        excluded part of the range) as <commit>.  Can be passed multiple