1GIT-MAILINFO(1) Git Manual GIT-MAILINFO(1)
2
6 git-mailinfo - Extracts patch and authorship from a single e-mail
7 message
8
10 git mailinfo [-k|-b] [-u | --encoding=<encoding> | -n]
11 [--[no-]scissors] [--quoted-cr=<action>]
12 <msg> <patch>
13
15 Reads a single e-mail message from the standard input, and writes the
16 commit log message in <msg> file, and the patches in <patch> file. The
17 author name, e-mail and e-mail subject are written out to the standard
18 output to be used by git am to create a commit. It is usually not
19 necessary to use this command directly. See git-am(1) instead.
20
22 -k
23 Usually the program removes email cruft from the Subject: header
24 line to extract the title line for the commit log message. This
25 option prevents this munging, and is most useful when used to read
26 back git format-patch -k output.
27 Specifically, the following are removed until none of them remain:
29 • Leading and trailing whitespace.
31 • Leading Re:, re:, and :.
33 • Leading bracketed strings (between [ and ], usually [PATCH]).
35 Finally, runs of whitespace are normalized to a single ASCII space
37 character.
38 -b
40 When -k is not in effect, all leading strings bracketed with [ and
41 ] pairs are stripped. This option limits the stripping to only the
42 pairs whose bracketed string contains the word "PATCH".
43 -u
45 The commit log message, author name and author email are taken from
46 the e-mail, and after minimally decoding MIME transfer encoding,
47 re-coded in the charset specified by i18n.commitEncoding
48 (defaulting to UTF-8) by transliterating them. This used to be
49 optional but now it is the default.
50 Note that the patch is always used as-is without charset
52 conversion, even with this flag.
53 --encoding=<encoding>
55 Similar to -u. But when re-coding, the charset specified here is
56 used instead of the one specified by i18n.commitEncoding or UTF-8.
57 -n
59 Disable all charset re-coding of the metadata.
60 -m, --message-id
62 Copy the Message-ID header at the end of the commit message. This
63 is useful in order to associate commits with mailing list
64 discussions.
65 --scissors
67 Remove everything in body before a scissors line (e.g. "-- >8 --").
68 The line represents scissors and perforation marks, and is used to
69 request the reader to cut the message at that line. If that line
70 appears in the body of the message before the patch, everything
71 before it (including the scissors line itself) is ignored when this
72 option is used.
73 This is useful if you want to begin your message in a discussion
75 thread with comments and suggestions on the message you are
76 responding to, and to conclude it with a patch submission,
77 separating the discussion and the beginning of the proposed commit
78 log message with a scissors line.
79 This can be enabled by default with the configuration option
81 mailinfo.scissors.
82 --no-scissors
84 Ignore scissors lines. Useful for overriding mailinfo.scissors
85 settings.
86 --quoted-cr=<action>
88 Action when processes email messages sent with base64 or
89 quoted-printable encoding, and the decoded lines end with a CRLF
90 instead of a simple LF.
91 The valid actions are:
93 • nowarn: Git will do nothing when such a CRLF is found.
95 • warn: Git will issue a warning for each message if such a CRLF
97 is found.
98 • strip: Git will convert those CRLF to LF.
100 The default action could be set by configuration option
102 mailinfo.quotedCR. If no such configuration option has been set,
103 warn will be used.
104 <msg>
106 The commit log message extracted from e-mail, usually except the
107 title line which comes from e-mail Subject.
108 <patch>
110 The patch extracted from e-mail.
111
113 Part of the git(1) suite
114Git 2.33.1 2021-10-12 GIT-MAILINFO(1)