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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
