Thread (4 messages) flat view 4 messages, 3 authors, 2016-06-15

Re: [PATCH] Include rev-list options in git-log manpage.

From: Johannes Sixt <hidden>
Date: 2016-06-15 22:44:06

Possibly related (same subject, not in this thread)

Miklos Vajna schrieb:
 Documentation/git-log.txt          |    6 +-
 Documentation/git-rev-list.txt     |  358 +-----------------------------------
 Documentation/rev-list-options.txt |  364 ++++++++++++++++++++++++++++++++++++
 3 files changed, 367 insertions(+), 361 deletions(-)
 create mode 100644 Documentation/rev-list-options.txt
Had you used format-patch -C then the patch would have been shorter by
~240 lines. And it would have been immediately obvious that you have put
this inside ifndef::gitlog[] brackets:
+ifndef::git-log[]
+--first-parent::
+	Follow only the first parent commit upon seeing a merge
+	commit.  This option can give a better overview when
+	viewing the evolution of a particular topic branch,
+	because merges into a topic branch tend to be only about
+	adjusting to updated upstream from time to time, and
+	this option allows you to ignore the individual commits
+	brought in to your history by such a merge.
+endif::git-log[]
I wonder why these brackets are necessary. This text applies to git-log,
too, no? Can't you just remove that paragraph from git-log.txt?

-- Hannes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help