Re: [PATCH 4/5] git-log.txt: rewrite note on why "--" may be required
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Apr 21, 2013, 08:09 UTC
- Message-ID
- <20130421080907.GF10429@elie.Belkin>
- In-Reply-To
- <CALkWK0kEngwYQieR=Xmvzu+XqBe+ZFxiWj0C8M-euFavDDaD2Q@mail.gmail.com>
Ramkumar Ramachandra wrote:
> I would say the most technically accurate > description of what 'git log' takes is a "committish range" (basically > a "revision range" that resolves to commits).
What is a revision range that doesn't resolve to commits? Am I wrong in thinking revision is nothing more than a synonym for commit?
When gitrevisions(7) says "A revision parameter <rev> typically, but not necessarily, names a commit object", I suspect it is residue from 3a45f625 trying to apologize for the extended SHA1 syntax parser being called "git rev-parse" instead of "git object-name-parse".