Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
- 2.50.1 → 2.51.2 no changes
- 
        2.50.0
          
            
                                 2025-06-16 2025-06-16
- 2.35.1 → 2.49.1 no changes
- 
        2.35.0
          
            
                             2022-01-24 2022-01-24
- 2.29.1 → 2.34.8 no changes
- 
        2.29.0
          
            
                                     2020-10-19 2020-10-19
- 2.18.1 → 2.28.1 no changes
- 
        2.18.0
          
            
                             2018-06-21 2018-06-21
- 2.11.4 → 2.17.6 no changes
- 
        2.10.5
          
            
                             2017-09-22 2017-09-22
- 2.7.6 → 2.9.5 no changes
- 
        2.6.7
          
            
                                 2017-05-05 2017-05-05
- 2.5.6 no changes
- 
        2.4.12
          
            
                             2017-05-05 2017-05-05
- 2.1.4 → 2.3.10 no changes
- 
        2.0.5
          
            
                                     2014-12-17 2014-12-17
SYNOPSIS
git fmt-merge-msg [-m <message>] [--log[=<n>] | --no-log] git fmt-merge-msg [-m <message>] [--log[=<n>] | --no-log] -F <file>
DESCRIPTION
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 <merge-message> argument of git merge.
This command is intended mostly for internal use by scripts automatically invoking git merge.
OPTIONS
- --log[=<n>]
- 
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 merge.logconfiguration variable.
- --no-log
- 
Do not list one-line descriptions from the actual commits being merged. 
- --[no-]summary
- 
Synonyms to --log and --no-log; these are deprecated and will be removed in the future. 
- -m <message>
- --message <message>
- 
Use <message> instead of the branch names for the first line of the log message. For use with --log.
- -F <file>
- --file <file>
- 
Take the list of merged objects from <file> instead of stdin. 
CONFIGURATION
- merge.branchdesc
- 
In addition to branch names, populate the log message with the branch description text associated with them. Defaults to false. 
- merge.log
- 
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. 
- merge.summary
- 
Synonym to merge.log; this is deprecated and will be removed in the future.
EXAMPLE
$ git fetch origin master $ git fmt-merge-msg --log <$GIT_DIR/FETCH_HEAD
Print a log message describing a merge of the "master" branch from the "origin" remote.
GIT
Part of the git[1] suite
