Re: [PATCH 4/5] git-log.txt: rewrite note on why "--" may be required

From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Apr 21, 2013, 08:13 UTC
Message-ID: <CALkWK0mmvwnRzq5eYTzvZRmEwn7nyDLe5cJsV1iQvNnh1Y7xEw@mail.gmail.com>
In-Reply-To: <CAPc5daV39HsoRR2pj34Tz1kQKFVRrp+NZpMM2BremocqvToA+A@mail.gmail.com>

Junio C Hamano wrote:

> A revision range is a slice of history, so you don't need any further
> adjective.
>
> Please don't introduce new words that do not add any accuracies nor value.

I was just saying: I don't want to introduce new terms either. I think revisions.txt needs to be fixed. Under the Specifying Ranges section:

'<rev>'::
	Include commits that are reachable from (i.e. ancestors of)
	<rev>.

This doesn't make sense because <rev> might as well refer to a blob*. So this should say s/<rev>/<rev> that names a commit object/.

* The first line in the Specifying Revisions section: A revision
parameter '<rev>' typically, but not necessarily, names a commit
object.