rev-list-options: clarify the usage of --reverse
Users often wonder if the oldest or the newest n commits are shown by `log -n --reverse`. Clarify that --reverse kicks in only after deciding which commits are to be shown to unconfuse them. Reported-by: Ruediger Meier <sweet_f_a@gmx.de> Signed-off-by: Pranit Bauva <pranit.bauva@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Pranit Bauva committed
Sep 27, 2016 at 20:44 UTC
04be69478fda74fbce91a6775e5b5946c3cde61e
1 file changed
+3
-2
Documentation/rev-list-options.txt
+3
-2
@@ -638,8 +638,9 @@ avoid showing the commits from two parallel development track mixed
638
together.
639
640
--reverse::
641
- Output the commits in reverse order.
642
- Cannot be combined with `--walk-reflogs`.
641
+ Output the commits chosen to be shown (see Commit Limiting
642
+ section above) in reverse order. Cannot be combined with
643
+ `--walk-reflogs`.
644
645
Object Traversal
646
~~~~~~~~~~~~~~~~