From: Koosha Khajehmoogahi <koosha@posteo.de>
To: git@vger.kernel.org
Cc: sunshine@sunshineco.com
Subject: [PATCH v2 3/5] Documentation: add git-log --merges= option and log.merges config. var
Date: Sat, 4 Apr 2015 03:21:59 +0200 [thread overview]
Message-ID: <1428110521-31028-3-git-send-email-koosha@posteo.de> (raw)
In-Reply-To: <1428110521-31028-1-git-send-email-koosha@posteo.de>
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Koosha Khajehmoogahi <koosha@posteo.de>
---
Documentation/git-log.txt | 3 +++
Documentation/rev-list-options.txt | 18 +++++++++++++++---
2 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 18bc716..e16f0f8 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -190,6 +190,9 @@ log.showRoot::
`git log -p` output would be shown without a diff attached.
The default is `true`.
+log.merges::
+ Default for `--merges=` option. Defaults to `show`.
+
mailmap.*::
See linkgit:git-shortlog[1].
diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
index f620ee4..0bb2390 100644
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -96,12 +96,24 @@ if it is part of the log message.
--remove-empty::
Stop when a given path disappears from the tree.
+--merges={show|hide|only}::
++
+--
+`show`: show both merge and non-merge commits
+
+`hide`: only show non-merge commits; same as `--max-parents=1`
+
+`only`: only show merge commits; same as `--min-parents=2`
+
+If `--merges=` is not specified, default value is `show`.
+--
++
+
--merges::
- Print only merge commits. This is exactly the same as `--min-parents=2`.
+ Shorthand for `--merges=only`.
--no-merges::
- Do not print commits with more than one parent. This is
- exactly the same as `--max-parents=1`.
+ Shorthand for `--merges=hide`.
--min-parents=<number>::
--max-parents=<number>::
--
2.3.3.263.g095251d.dirty
next prev parent reply other threads:[~2015-04-04 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <266077>
2015-04-04 1:21 ` [PATCH v2 1/5] revision: add --merges={show|only|hide} option Koosha Khajehmoogahi
2015-04-04 1:21 ` [PATCH v2 2/5] log: honor log.merges= option Koosha Khajehmoogahi
2015-04-04 20:00 ` Junio C Hamano
2015-04-07 22:15 ` Koosha Khajehmoogahi
2015-04-08 2:28 ` Junio C Hamano
2015-04-08 10:42 ` Koosha Khajehmoogahi
2015-04-13 4:56 ` Junio C Hamano
2015-04-07 5:18 ` Eric Sunshine
2015-04-04 1:21 ` Koosha Khajehmoogahi [this message]
2015-04-05 21:41 ` [PATCH v2 3/5] Documentation: add git-log --merges= option and log.merges config. var Junio C Hamano
2015-04-04 1:22 ` [PATCH v2 4/5] t4202-log: add tests for --merges= Koosha Khajehmoogahi
2015-04-07 7:32 ` Eric Sunshine
2015-04-04 1:22 ` [PATCH v2 5/5] bash-completion: add support for git-log --merges= and log.merges Koosha Khajehmoogahi
2015-04-07 5:16 ` [PATCH v2 1/5] revision: add --merges={show|only|hide} option Eric Sunshine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428110521-31028-3-git-send-email-koosha@posteo.de \
--to=koosha@posteo.de \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).