man pages section 1: User Commands

Exit Print View

Updated: July 2014

git-mailinfo (1)


git-mailinfo - Extracts patch and authorship from a single e-mail message


git mailinfo [-k|-b] [-u | --encoding=<encoding> | -n] [--scissors] <msg> <patch>


Git Manual                                        GIT-MAILINFO(1)

     git-mailinfo - Extracts patch and authorship from a single
     e-mail message

     git mailinfo [-k|-b] [-u | --encoding=<encoding> | -n] [--scissors] <msg> <patch>

     Reads a single e-mail message from the standard input, and
     writes the commit log message in <msg> file, and the patches
     in <patch> file. The author name, e-mail and e-mail subject
     are written out to the standard output to be used by git am
     to create a commit. It is usually not necessary to use this
     command directly. See git-am(1) instead.

         Usually the program removes email cruft from the
         Subject: header line to extract the title line for the
         commit log message. This option prevents this munging,
         and is most useful when used to read back git
         format-patch -k output.

         Specifically, the following are removed until none of
         them remain:

         o   Leading and trailing whitespace.

         o   Leading Re:, re:, and :.

         o   Leading bracketed strings (between [ and ], usually

         Finally, runs of whitespace are normalized to a single
         ASCII space character.

         When -k is not in effect, all leading strings bracketed
         with [ and ] pairs are stripped. This option limits the
         stripping to only the pairs whose bracketed string
         contains the word "PATCH".

         The commit log message, author name and author email are
         taken from the e-mail, and after minimally decoding MIME
         transfer encoding, re-coded in the charset specified by
         i18n.commitencoding (defaulting to UTF-8) by
         transliterating them. This used to be optional but now
         it is the default.

         Note that the patch is always used as-is without charset

Git          Last change: 02/22/2012                    1

Git Manual                                        GIT-MAILINFO(1)

         conversion, even with this flag.

         Similar to -u. But when re-coding, the charset specified
         here is used instead of the one specified by
         i18n.commitencoding or UTF-8.

         Disable all charset re-coding of the metadata.

         Remove everything in body before a scissors line. A line
         that mainly consists of scissors (either ">8" or "8<")
         and perforation (dash "-") marks is called a scissors
         line, and is used to request the reader to cut the
         message at that line. If such a line appears in the body
         of the message before the patch, everything before it
         (including the scissors line itself) is ignored when
         this option is used.

         This is useful if you want to begin your message in a
         discussion thread with comments and suggestions on the
         message you are responding to, and to conclude it with a
         patch submission, separating the discussion and the
         beginning of the proposed commit log message with a
         scissors line.

         This can enabled by default with the configuration
         option mailinfo.scissors.

         Ignore scissors lines. Useful for overriding
         mailinfo.scissors settings.

         The commit log message extracted from e-mail, usually
         except the title line which comes from e-mail Subject.

         The patch extracted from e-mail.

     Part of the git(1) suite

     See attributes(5) for descriptions of the following

Git          Last change: 02/22/2012                    2

Git Manual                                        GIT-MAILINFO(1)

     |Availability   | developer/versioning/git |
     |Stability      | Uncommitted              |
     This software was built from source available at  The original
     community source was downloaded from  http://git-

     Further information about this software can be found on the
     open source community website at

Git          Last change: 02/22/2012                    3