From: "Pranit Bauva" <pranit.ba...@gmail.com>
Specify even more clearly that --reverse works only with the commits
which are chosen to be shown so as to eliminate the confusion as to
whether the first n or the last n commits with be shown when used
hi Pranit,
micro-nit: 'first' and 'last' can be tricky to distinguish for lists (e.g.
of commits) that can be considered from both ends with equal ease (people
are so easily confused ;-). In such cases its always worth stating the sort
order mechanism (within the appropriate sentence). However, in this case the
clarification is to clearly point elsewhere, so I'm OK with the patch.
with `-n --reverse`.
Reported-by: Ruediger Meier <sweet_...@gmx.de>
Signed-off-by: Pranit Bauva <pranit.ba...@gmail.com>
---
Documentation/rev-list-options.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/rev-list-options.txt
b/Documentation/rev-list-options.txt
index 7e462d3..5da7cf5 100644
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -657,8 +657,9 @@ avoid showing the commits from two parallel
development track mixed
together.
--reverse::
- Output the commits in reverse order.
- Cannot be combined with `--walk-reflogs`.
+ Output the commits chosen to be shown (see Commit Limiting
+ section above) in reverse order. Cannot be combined with
+ `--walk-reflogs`.
Object Traversal
~~~~~~~~~~~~~~~~
--
https://github.com/git/git/pull/296
--
Philip
