2 .\" Title: git-mailinfo
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
7 .\" Source: Git 2.46.1.603.g94b60adee3
10 .TH "GIT\-MAILINFO" "1" "2024-09-20" "Git 2\&.46\&.1\&.603\&.g94b60a" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 git-mailinfo \- Extracts patch and authorship from a single e\-mail message
35 \fIgit mailinfo\fR [\-k|\-b] [\-u | \-\-encoding=<encoding> | \-n]
36 [\-\-[no\-]scissors] [\-\-quoted\-cr=<action>]
41 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 \fIgit am\fR to create a commit\&. It is usually not necessary to use this command directly\&. See \fBgit-am\fR(1) instead\&.
46 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
47 \fIgit format\-patch \-k\fR
50 Specifically, the following are removed until none of them remain:
60 Leading and trailing whitespace\&.
85 Leading bracketed strings (between
92 Finally, runs of whitespace are normalized to a single ASCII space character\&.
97 When \-k is not in effect, all leading strings bracketed with
101 pairs are stripped\&. This option limits the stripping to only the pairs whose bracketed string contains the word "PATCH"\&.
106 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
107 \fBi18n\&.commitEncoding\fR
108 (defaulting to UTF\-8) by transliterating them\&. This used to be optional but now it is the default\&.
110 Note that the patch is always used as\-is without charset conversion, even with this flag\&.
113 \-\-encoding=<encoding>
115 Similar to \-u\&. But when re\-coding, the charset specified here is used instead of the one specified by
116 \fBi18n\&.commitEncoding\fR
122 Disable all charset re\-coding of the metadata\&.
127 Copy the Message\-ID header at the end of the commit message\&. This is useful in order to associate commits with mailing list discussions\&.
132 Remove everything in body before a scissors line (e\&.g\&. "\-\- >8 \-\-")\&. The line represents scissors and perforation marks, and is used to request the reader to cut the message at that line\&. If that 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\&.
134 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 line\&.
136 This can be enabled by default with the configuration option mailinfo\&.scissors\&.
141 Ignore scissors lines\&. Useful for overriding mailinfo\&.scissors settings\&.
144 \-\-quoted\-cr=<action>
146 Action when processes email messages sent with base64 or quoted\-printable encoding, and the decoded lines end with a CRLF instead of a simple LF\&.
148 The valid actions are:
158 \fBnowarn\fR: Git will do nothing when such a CRLF is found\&.
169 \fBwarn\fR: Git will issue a warning for each message if such a CRLF is found\&.
180 \fBstrip\fR: Git will convert those CRLF to LF\&.
183 The default action could be set by configuration option
184 \fBmailinfo\&.quotedCR\fR\&. If no such configuration option has been set,
191 The commit log message extracted from e\-mail, usually except the title line which comes from e\-mail Subject\&.
196 The patch extracted from e\-mail\&.
200 Everything below this line in this section is selectively included from the \fBgit-config\fR(1) documentation\&. The content is the same as what\(cqs found there:
205 \fBgit-mailinfo\fR(1)
207 \fBgit-am\fR(1)) act by default as if the \-\-scissors option was provided on the command\-line\&. When active, this feature removes everything from the message body before a scissors line (i\&.e\&. consisting mainly of ">8", "8<" and "\-")\&.
211 Part of the \fBgit\fR(1) suite