git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-rev-list.txt: rev stands for revision, not reverse.
Date: Thu, 01 Nov 2007 12:51:11 -0700	[thread overview]
Message-ID: <7vr6j9bv80.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071101084552.GA4934@ins.uni-bonn.de> (Ralf Wildenhues's message of "Thu, 1 Nov 2007 09:45:53 +0100")

Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:

> Mention revs, revisions as aliases for commit objects,
> to clarify that rev-list is not an abbreviation for
> listing in reverse order, but for listing revisions.
> ---
> Yes, believe it or not, but I stumbled over the synopsis
>
> | git-rev-list - Lists commit objects in reverse chronological order
>
> asking myself whether rev could possibly mean "reverse".
> I hope this helps avoid this pitfall for others.

In addition to your patch,

	git-rev-list - List commits from most recent to older

might be a good rewording?  "rev-list --reverse" reverses that
usual order and we end up explaining double reversal if we use
the phrase "reverse chronological order" to describe the normal
order.

  reply	other threads:[~2007-11-01 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  8:45 [PATCH] git-rev-list.txt: rev stands for revision, not reverse Ralf Wildenhues
2007-11-01 19:51 ` Junio C Hamano [this message]
2007-11-02 18:55   ` Ralf Wildenhues
2007-11-02 20:12     ` Junio C Hamano
2007-11-02 20:46       ` Junio C Hamano

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=7vr6j9bv80.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=git@vger.kernel.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).