From: Pranit Bauva Date: Tue, 27 Sep 2016 14:10:22 GMT Subject: [PATCH] rev-list-options: clarify the usage of -n/--max-number Message-ID: <010201576bfb6c7d-0b68228f-9503-4dd1-9721-713477fa2596-000000@eu-west-1.amazonses.com> In-Reply-To: <201609271240.19759.sweet_f_a@gmx.de> -n=, -, --max-number= shows the last n commits specified in irrespective of whether --reverse is used or not. With --reverse, it just shows the last n commits in reverse order. Reported-by: Ruediger Meier Signed-off-by: Pranit Bauva --- Hey Ruegiger, The description is a bit inappropriate for --max-count and thus this patch. I cannot comment whether --max-count=-n would be a good choice or not because personally I never left the need of it. I normally use --reverse so as to review my patches in a branch serially. So for me the current usage of --reverse seems more appropriate. --- Documentation/rev-list-options.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt index 7e462d3..6b7c2e5 100644 --- a/Documentation/rev-list-options.txt +++ b/Documentation/rev-list-options.txt @@ -18,7 +18,7 @@ ordering and formatting options, such as `--reverse`. -:: -n :: --max-count=:: - Limit the number of commits to output. + Limit to last n number of commits to output specified in . --skip=:: Skip 'number' commits before starting to show the commit output. -- https://github.com/git/git/pull/296