2 .\" Title: git-fmt-merge-msg
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
10 .TH "GIT\-FMT\-MERGE\-MSG" "1" "2023\-06\-01" "Git 2\&.41\&.0" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 git-fmt-merge-msg \- Produce a merge commit message
35 \fIgit fmt\-merge\-msg\fR [\-m <message>] [\-\-into\-name <branch>] [\-\-log[=<n>] | \-\-no\-log]
36 \fIgit fmt\-merge\-msg\fR [\-m <message>] [\-\-log[=<n>] | \-\-no\-log] \-F <file>
41 Takes the list of merged objects on stdin and produces a suitable commit message to be used for the merge commit, usually to be passed as the \fI<merge\-message>\fR argument of \fIgit merge\fR\&.
43 This command is intended mostly for internal use by scripts automatically invoking \fIgit merge\fR\&.
48 In addition to branch names, populate the log message with one\-line descriptions from the actual commits that are being merged\&. At most <n> commits from each merge parent will be used (20 if <n> is omitted)\&. This overrides the
50 configuration variable\&.
55 Do not list one\-line descriptions from the actual commits being merged\&.
60 Synonyms to \-\-log and \-\-no\-log; these are deprecated and will be removed in the future\&.
63 \-m <message>, \-\-message <message>
65 Use <message> instead of the branch names for the first line of the log message\&. For use with
69 \-\-into\-name <branch>
71 Prepare the merge message as if merging to the branch
72 \fB<branch>\fR, instead of the name of the real branch to which the merge is made\&.
75 \-F <file>, \-\-file <file>
77 Take the list of merged objects from <file> instead of stdin\&.
83 In addition to branch names, populate the log message with the branch description text associated with them\&. Defaults to false\&.
88 In addition to branch names, populate the log message with at most the specified number of one\-line descriptions from the actual commits that are being merged\&. Defaults to false, and true is a synonym for 20\&.
93 By adding a glob that matches the names of integration branches to this multi\-valued configuration variable, the default merge message computed for merges into these integration branches will omit "into <branch name>" from its title\&.
95 An element with an empty value can be used to clear the list of globs accumulated from previous configuration entries\&. When there is no
96 \fBmerge\&.suppressDest\fR
97 variable defined, the default value of
99 is used for backward compatibility\&.
105 \fBmerge\&.log\fR; this is deprecated and will be removed in the future\&.
113 $ git fetch origin master
114 $ git fmt\-merge\-msg \-\-log <$GIT_DIR/FETCH_HEAD
121 Print a log message describing a merge of the "master" branch from the "origin" remote\&.
127 Part of the \fBgit\fR(1) suite