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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
