From: Pranit Bauva <pranit.bauva@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Philip Oakley <philipoakley@iee.org>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH v2] rev-list-options: clarify the usage of --reverse
Date: Wed, 28 Sep 2016 07:22:47 +0530 [thread overview]
Message-ID: <CAFZEwPMe=eLbazZcj8Ce5m01VCt+V2sSix5B_spYRzz7cqsOOw@mail.gmail.com> (raw)
In-Reply-To: <xmqqoa39kn57.fsf@gitster.mtv.corp.google.com>
Hey Junio,
On Wed, Sep 28, 2016 at 3:42 AM, Junio C Hamano <gitster@pobox.com> wrote:
> "Philip Oakley" <philipoakley@iee.org> writes:
>
>> micro-nit: 'first' and 'last' can be tricky to distinguish for lists...
>
> Let's do this then.
>
> -- >8 --
> From: Pranit Bauva <pranit.bauva@gmail.com>
> 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@gmx.de>
> Signed-off-by: Pranit Bauva <pranit.bauva@gmail.com>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
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
>
prev parent reply other threads:[~2016-09-28 1:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 10:40 question about git rev-list --max-count=n Ruediger Meier
2016-09-27 14:10 ` [PATCH] rev-list-options: clarify the usage of -n/--max-number Pranit Bauva
2016-09-27 16:51 ` Junio C Hamano
2016-09-27 20:32 ` Pranit Bauva
2016-09-27 20:44 ` [PATCH v2] rev-list-options: clarify the usage of --reverse Pranit Bauva
2016-09-27 21:51 ` Philip Oakley
2016-09-27 22:12 ` Junio C Hamano
2016-09-27 22:21 ` Philip Oakley
2016-09-28 1:52 ` Pranit Bauva [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFZEwPMe=eLbazZcj8Ce5m01VCt+V2sSix5B_spYRzz7cqsOOw@mail.gmail.com' \
--to=pranit.bauva@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).