git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 21, 2013, 08:33 UTC
Message-ID
<7vvc7guvu4.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130421080907.GF10429@elie.Belkin>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 13 quoted lines
> 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".
 - A revision range is a slice of history.  There is no need for
   "committish revision range" as there is no other kinds of ranges.
 - A revision should be a synonym to a committish, as glossary
   defines.  We historically used "revision" more or less
   interchangeably with "object name", especially "an extended SHA-1
   expression that is used as an object name", to mean whatever
   get_sha1() can grok down to a single object name.  This must be
   rectified to avoid causing confusion to new readers of our
   documentation.
 - Documentation/revisions.txt needs to be cleaned up.  It lists
   "specifying revisions" and "specifying ranges", which is a good
   start primarily because some notations used in ranges are not
   revisions (e.g. "^C"), but it should have three (not two) sections.
   They are: "specifying revisions", "specifying object names", and
   "specifying ranges".  Move non committish specification such as
   <revision>:<path> from the current "specifying revisions" section
   and make the new "object names" section.  The "ranges" section is
   already written in terms of revisions, and does not need any
   update, once we clarify the definition of a "revision" as
   "committish".
Previous: Jonathan NiederNext: Ramkumar Ramachandra
Message 20 of 35 in “Documentation/shortlog improvements”
  1. 0/5 Documentation/shortlog improvementsRamkumar Ramachandra, Apr 20, 2013
  2. 1/5 git-shortlog.txt: remove (-h|--help) from OPTIONSRamkumar Ramachandra, Apr 20, 2013
  3. 2/5 builtin/shortlog.c: make usage string consistent with logRamkumar Ramachandra, Apr 20, 2013
  4. 3/5 git-log.txt: fix description of <since>..<until>Ramkumar Ramachandra, Apr 20, 2013
  5. Jonathan NiederApr 20, 2013
  6. Ramkumar RamachandraApr 21, 2013
  7. Jonathan NiederApr 21, 2013
  8. Junio C HamanoApr 21, 2013
  9. Junio C HamanoApr 21, 2013
  10. 4/5 git-log.txt: rewrite note on why "--" may be requiredRamkumar Ramachandra, Apr 20, 2013
  11. Junio C HamanoApr 21, 2013
  12. Ramkumar RamachandraApr 21, 2013
  13. Junio C HamanoApr 21, 2013
  14. Ramkumar RamachandraApr 21, 2013
  15. Junio C HamanoApr 21, 2013
  16. Ramkumar RamachandraApr 21, 2013
  17. Jonathan NiederApr 21, 2013
  18. Ramkumar RamachandraApr 21, 2013
  19. Jonathan NiederApr 21, 2013
  20. Junio C HamanoApr 21, 2013
  21. Ramkumar RamachandraApr 21, 2013
  22. Ramkumar RamachandraApr 21, 2013
  23. Jonathan NiederApr 21, 2013
  24. Junio C HamanoApr 21, 2013
  25. Ramkumar RamachandraApr 21, 2013
  26. Junio C HamanoApr 22, 2013
  27. Thomas RastApr 22, 2013
  28. Thomas RastApr 22, 2013
  29. Junio C HamanoApr 22, 2013
  30. 5/5 git-shortlog.txt: make SYNOPSIS match log, update OPTIONSRamkumar Ramachandra, Apr 20, 2013
  31. Junio C HamanoApr 21, 2013
  32. Ramkumar RamachandraApr 21, 2013
  33. Ramkumar RamachandraApr 21, 2013
  34. glossary: a revision is just a commitJonathan Nieder, Apr 21, 2013
  35. Junio C HamanoApr 21, 2013

Read the whole thread, see it on lore, or plain text.

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