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 22, 2013, 02:40 UTC
Message-ID
<7vmwsrqocu.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7vtxn0wf4j.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 8 quoted lines
> Two other things I noticed with the current text are:
> ...
>  * 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.

This is a minimalistic patch to fix the formatting. I removed the extra sentence after the enumeration and moved it to the end of the main text, but somebody may have a better idea to persuade AsciiDoc to format it in a more reasonable way while keeping the sentence there.

-- >8 --
Subject: line-log: fix documentation formatting

The second paragraph of the added description for the -L option "<start> and <end> can take one of these forms:", and the list of forms that follow the headline, were indented one level too short, due to the missing "+" to signal that the next paragraph continues the previous one.

Also "You can specify this option more than once" is about the -L option, not about its various forms of starting and ending points. Move it to the end of the main text.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/git-log.txt | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 4850226..0959f9d 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -76,12 +76,11 @@ produced by --stat etc.
 	not give any pathspec limiters.  This is currently limited to
 	a walk starting from a single revision, i.e., you may only
 	give zero or one positive revision arguments.
-
+	You can specify this option more than once.
++
 <start> and <end> can take one of these forms:
 
 include::line-range-format.txt[]
-You can specify this option more than once.
-
 
 --full-line-diff::
 	Always print the interesting range even if the current commit
Previous: Ramkumar RamachandraNext: Thomas Rast
Message 26 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.