1GIT-MAILINFO(1) Git Manual GIT-MAILINFO(1)
2
3
4
6 git-mailinfo - Extracts patch and authorship from a single e-mail
7 message
8
10 git mailinfo [-k|-b] [-u | --encoding=<encoding> | -n] [--[no-]scissors] <msg> <patch>
11
13 Reads a single e-mail message from the standard input, and writes the
14 commit log message in <msg> file, and the patches in <patch> file. The
15 author name, e-mail and e-mail subject are written out to the standard
16 output to be used by git am to create a commit. It is usually not
17 necessary to use this command directly. See git-am(1) instead.
18
20 -k
21 Usually the program removes email cruft from the Subject: header
22 line to extract the title line for the commit log message. This
23 option prevents this munging, and is most useful when used to read
24 back git format-patch -k output.
25
26 Specifically, the following are removed until none of them remain:
27
28 · Leading and trailing whitespace.
29
30 · Leading Re:, re:, and :.
31
32 · Leading bracketed strings (between [ and ], usually [PATCH]).
33
34 Finally, runs of whitespace are normalized to a single ASCII space
35 character.
36
37 -b
38 When -k is not in effect, all leading strings bracketed with [ and
39 ] pairs are stripped. This option limits the stripping to only the
40 pairs whose bracketed string contains the word "PATCH".
41
42 -u
43 The commit log message, author name and author email are taken from
44 the e-mail, and after minimally decoding MIME transfer encoding,
45 re-coded in the charset specified by i18n.commitencoding
46 (defaulting to UTF-8) by transliterating them. This used to be
47 optional but now it is the default.
48
49 Note that the patch is always used as-is without charset
50 conversion, even with this flag.
51
52 --encoding=<encoding>
53 Similar to -u. But when re-coding, the charset specified here is
54 used instead of the one specified by i18n.commitencoding or UTF-8.
55
56 -n
57 Disable all charset re-coding of the metadata.
58
59 -m, --message-id
60 Copy the Message-ID header at the end of the commit message. This
61 is useful in order to associate commits with mailing list
62 discussions.
63
64 --scissors
65 Remove everything in body before a scissors line. A line that
66 mainly consists of scissors (either ">8" or "8<") and perforation
67 (dash "-") marks is called a scissors line, and is used to request
68 the reader to cut the message at that line. If such a line appears
69 in the body of the message before the patch, everything before it
70 (including the scissors line itself) is ignored when this option is
71 used.
72
73 This is useful if you want to begin your message in a discussion
74 thread with comments and suggestions on the message you are
75 responding to, and to conclude it with a patch submission,
76 separating the discussion and the beginning of the proposed commit
77 log message with a scissors line.
78
79 This can be enabled by default with the configuration option
80 mailinfo.scissors.
81
82 --no-scissors
83 Ignore scissors lines. Useful for overriding mailinfo.scissors
84 settings.
85
86 <msg>
87 The commit log message extracted from e-mail, usually except the
88 title line which comes from e-mail Subject.
89
90 <patch>
91 The patch extracted from e-mail.
92
94 Part of the git(1) suite
95
96
97
98Git 2.26.2 2020-04-20 GIT-MAILINFO(1)