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, 07:33 UTC
Message-ID
<7v8v4cwd6g.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CALkWK0nFAzPPb0_jTRev6nuicCV81sRQAbe=277nhyyY8TnQ7A@mail.gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 7 quoted lines
> Junio C Hamano wrote:
>> I think "branch names" was an attempt to make it more newbie
>> friendly by sacrificing technical accuracy.  With the suggested
>> update (see the review for the previous one), it would be easier to
>> read if this part said "options or the revision range".
>
> Why does it have to be a range? It might well be a list of revisions,

Study "Specifying Ranges" section of gitrevisions and come back, perhaps?

A list of revisions is merely a way to specify "revision range" that are reachable from any of these revisions listed. "log A B" won't stop by just showing A and B (that would be "show A B"), but will list those that are reachable from A B, so in the context of discussing the arguments given to "git log" command, "A B" is still "revision range".

Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 13 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.