Mac Developer Library Developer


This manual page is part of Xcode Tools version 5.0

To obtain these tools:

If you are running a version of Xcode Tools other than 5.0, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

GIT-MAILINFO(1)                                  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] [--[no-]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:

              Leading and trailing whitespace.

              Leading Re:, re:, and :.

              Leading bracketed strings (between [ and ], usually [PATCH]).

           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 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

           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

Git 1.8.3                                        05/24/2013                                  GIT-MAILINFO(1)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.