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] [--scissors]
11 <msg> <patch>
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 cleans up the Subject: header line to extract
23 the title line for the commit log message, among which (1) remove
24 Re: or re:, (2) leading whitespaces, (3) [ up to ], typically
25 [PATCH], and then prepends "[PATCH] ". This flag forbids this
26 munging, and is most useful when used to read back git format-patch
27 -k output.
28
29 -b
30 When -k is not in effect, all leading strings bracketed with [ and
31 ] pairs are stripped. This option limits the stripping to only the
32 pairs whose bracketed string contains the word "PATCH".
33
34 -u
35 The commit log message, author name and author email are taken from
36 the e-mail, and after minimally decoding MIME transfer encoding,
37 re-coded in the charset specified by i18n.commitencoding
38 (defaulting to UTF-8) by transliterating them. This used to be
39 optional but now it is the default.
40
41 Note that the patch is always used as-is without charset
42 conversion, even with this flag.
43
44 --encoding=<encoding>
45 Similar to -u. But when re-coding, the charset specified here is
46 used instead of the one specified by i18n.commitencoding or UTF-8.
47
48 -n
49 Disable all charset re-coding of the metadata.
50
51 --scissors
52 Remove everything in body before a scissors line. A line that
53 mainly consists of scissors (either ">8" or "8<") and perforation
54 (dash "-") marks is called a scissors line, and is used to request
55 the reader to cut the message at that line. If such a line appears
56 in the body of the message before the patch, everything before it
57 (including the scissors line itself) is ignored when this option is
58 used.
59
60 This is useful if you want to begin your message in a discussion
61 thread with comments and suggestions on the message you are
62 responding to, and to conclude it with a patch submission,
63 separating the discussion and the beginning of the proposed commit
64 log message with a scissors line.
65
66 This can enabled by default with the configuration option
67 mailinfo.scissors.
68
69 --no-scissors
70 Ignore scissors lines. Useful for overriding mailinfo.scissors
71 settings.
72
73 <msg>
74 The commit log message extracted from e-mail, usually except the
75 title line which comes from e-mail Subject.
76
77 <patch>
78 The patch extracted from e-mail.
79
81 Written by Linus Torvalds <torvalds@osdl.org[1]> and Junio C Hamano
82 <gitster@pobox.com[2]>
83
85 Documentation by Junio C Hamano and the git-list
86 <git@vger.kernel.org[3]>.
87
89 Part of the git(1) suite
90
92 1. torvalds@osdl.org
93 mailto:torvalds@osdl.org
94
95 2. gitster@pobox.com
96 mailto:gitster@pobox.com
97
98 3. git@vger.kernel.org
99 mailto:git@vger.kernel.org
100
101
102
103Git 1.7.4.4 04/11/2011 GIT-MAILINFO(1)