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