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, 06:51 UTC
Message-ID
<7vtxn0wf4j.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1366458313-7186-5-git-send-email-artagnon@gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 22 quoted lines
> In its current form, the note talks about separating options from
> "branch names" and "refnames" in the same sentence.  This is entirely
> inaccurate, as the rev spec need not be a set of branch names or ref
> names.  Rewrite it to use the word "revisions".
>
> Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
> ---
>  Documentation/git-log.txt | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
> index f03ae74..1a9c3ca 100644
> --- a/Documentation/git-log.txt
> +++ b/Documentation/git-log.txt
> @@ -75,8 +75,8 @@ produced by --stat etc.
>  	Simplification" below for details and other simplification
>  	modes.
>  +
> -To prevent confusion with options and branch names, paths may need to
> -be prefixed with "\-- " to separate them from options or refnames.
> +Paths may need to be prefixed with "\-- " to separate them from
> +options or revisions, when confusion arises.

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

Two other things I noticed with the current text are:
 * As the synopsis section shows, on the command line, --options
   come first, then revision range and then pathspec.  The order of
   the description should follow that as well.  The current text
   shows <since>..<until> at the very beginning, which is wrong.
 * The part with the new "-L" option seems to be throwing the
   overall formatting off.  Its second paragraph "<start> and <end>
   can take..." is not indented to the same level as its first
   paragraph "Trace the evolution of...", and the following items,
   like "--full-line-diff" and "[--] <pathspec>..." are indented one
   level too deeply.
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 11 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.