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:23 UTC
Message-ID: <CALkWK0n+Q6EWy6StGvgwvLf5mZqZfhaCvG70zD=2a0rK3qRLCQ@mail.gmail.com>
In-Reply-To: <CALkWK0mmvwnRzq5eYTzvZRmEwn7nyDLe5cJsV1iQvNnh1Y7xEw@mail.gmail.com>

Ramkumar Ramachandra wrote:

Show 6 quoted lines

> '<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.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.