1GIT-FMT-MERGE-MSG(1) Git Manual GIT-FMT-MERGE-MSG(1)
2
3
4
6 git-fmt-merge-msg - Produce a merge commit message
7
9 git fmt-merge-msg [-m <message>] [--log[=<n>] | --no-log] <$GIT_DIR/FETCH_HEAD
10 git fmt-merge-msg [-m <message>] [--log[=<n>] | --no-log] -F <file>
11
12
14 Takes the list of merged objects on stdin and produces a suitable
15 commit message to be used for the merge commit, usually to be passed as
16 the <merge-message> argument of git merge.
17
18 This command is intended mostly for internal use by scripts
19 automatically invoking git merge.
20
22 --log[=<n>]
23 In addition to branch names, populate the log message with one-line
24 descriptions from the actual commits that are being merged. At most
25 <n> commits from each merge parent will be used (20 if <n> is
26 omitted). This overrides the merge.log configuration variable.
27
28 --no-log
29 Do not list one-line descriptions from the actual commits being
30 merged.
31
32 --summary, --no-summary
33 Synonyms to --log and --no-log; these are deprecated and will be
34 removed in the future.
35
36 -m <message>, --message <message>
37 Use <message> instead of the branch names for the first line of the
38 log message. For use with --log.
39
40 -F <file>, --file <file>
41 Take the list of merged objects from <file> instead of stdin.
42
44 merge.log
45 In addition to branch names, populate the log message with at most
46 the specified number of one-line descriptions from the actual
47 commits that are being merged. Defaults to false, and true is a
48 synonym for 20.
49
50 merge.summary
51 Synonym to merge.log; this is deprecated and will be removed in the
52 future.
53
55 git-merge(1)
56
58 Written by Junio C Hamano <gitster@pobox.com[1]>
59
61 Documentation by Petr Baudis, Junio C Hamano and the git-list
62 <git@vger.kernel.org[2]>.
63
65 Part of the git(1) suite
66
68 1. gitster@pobox.com
69 mailto:gitster@pobox.com
70
71 2. git@vger.kernel.org
72 mailto:git@vger.kernel.org
73
74
75
76Git 1.7.4.4 04/11/2011 GIT-FMT-MERGE-MSG(1)