From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Sun, 21 Apr 2013 08:23:28 GMT
Subject: Re: [PATCH 4/5] git-log.txt: rewrite note on why "--" may be required
Message-ID: <CALkWK0n+Q6EWy6StGvgwvLf5mZqZfhaCvG70zD=2a0rK3qRLCQ@mail.gmail.com>
In-Reply-To: <CALkWK0mmvwnRzq5eYTzvZRmEwn7nyDLe5cJsV1iQvNnh1Y7xEw@mail.gmail.com>

Ramkumar Ramachandra wrote:
> '<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/.

In other words, my fix is to change the meaning of "revision range" to
not literally mean "range of revisions", but rather "range of
(revisions that are commits)".  I think it is more sensible than
Jonathan's fix which breaks too many existing things; most
significantly, the names rev-parse/rev-list.