Hey Junio, On Wed, Sep 28, 2016 at 3:42 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > "Philip Oakley" <philipoakley@xxxxxxx> writes: > >> micro-nit: 'first' and 'last' can be tricky to distinguish for lists... > > Let's do this then. > > -- >8 -- > From: Pranit Bauva <pranit.bauva@xxxxxxxxx> > Date: Tue, 27 Sep 2016 20:44:09 +0000 > Subject: [PATCH] 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@xxxxxx> > Signed-off-by: Pranit Bauva <pranit.bauva@xxxxxxxxx> > Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > --- Looks good! Thanks! > 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 4f009d4..f8946d4 100644 > --- a/Documentation/rev-list-options.txt > +++ b/Documentation/rev-list-options.txt > @@ -638,8 +638,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 > ~~~~~~~~~~~~~~~~ > -- > 2.10.0-561-g98a6b79 >