1 <?xml version="1.0" encoding="UTF-8"?>
\r
2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
\r
4 <article lang="en" id="git-mailinfo(1)">
\r
6 <title>git-mailinfo(1)</title>
\r
8 <primary>git-mailinfo(1)</primary>
\r
11 <simplesect id="_name">
\r
13 <simpara>git-mailinfo - Extracts patch and authorship from a single e-mail message</simpara>
\r
15 <simplesect id="_synopsis">
\r
16 <title>SYNOPSIS</title>
\r
18 <literallayout><emphasis>git mailinfo</emphasis> [-k|-b] [-u | --encoding=<encoding> | -n] [--scissors] <msg> <patch></literallayout>
\r
21 <simplesect id="_description">
\r
22 <title>DESCRIPTION</title>
\r
23 <simpara>Reads a single e-mail message from the standard input, and
\r
24 writes the commit log message in <msg> file, and the patches in
\r
25 <patch> file. The author name, e-mail and e-mail subject are
\r
26 written out to the standard output to be used by <emphasis>git am</emphasis>
\r
27 to create a commit. It is usually not necessary to use this
\r
28 command directly. See <xref linkend="git-am(1)" /> instead.</simpara>
\r
30 <simplesect id="_options">
\r
31 <title>OPTIONS</title>
\r
39 Usually the program removes email cruft from the Subject:
\r
40 header line to extract the title line for the commit log
\r
41 message. This option prevents this munging, and is most
\r
42 useful when used to read back <emphasis>git format-patch -k</emphasis> output.
\r
44 <simpara>Specifically, the following are removed until none of them remain:</simpara>
\r
48 Leading and trailing whitespace.
\r
53 Leading <emphasis>Re:</emphasis>, <emphasis>re:</emphasis>, and <emphasis>:</emphasis>.
\r
58 Leading bracketed strings (between <emphasis>[</emphasis> and <emphasis>]</emphasis>, usually
\r
59 <emphasis>[PATCH]</emphasis>).
\r
63 <simpara>Finally, runs of whitespace are normalized to a single ASCII space
\r
64 character.</simpara>
\r
73 When -k is not in effect, all leading strings bracketed with <emphasis>[</emphasis>
\r
74 and <emphasis>]</emphasis> pairs are stripped. This option limits the stripping to
\r
75 only the pairs whose bracketed string contains the word "PATCH".
\r
85 The commit log message, author name and author email are
\r
86 taken from the e-mail, and after minimally decoding MIME
\r
87 transfer encoding, re-coded in the charset specified by
\r
88 i18n.commitencoding (defaulting to UTF-8) by transliterating
\r
89 them. This used to be optional but now it is the default.
\r
91 <simpara>Note that the patch is always used as-is without charset
\r
92 conversion, even with this flag.</simpara>
\r
97 --encoding=<encoding>
\r
101 Similar to -u. But when re-coding, the charset specified here is
\r
102 used instead of the one specified by i18n.commitencoding or UTF-8.
\r
112 Disable all charset re-coding of the metadata.
\r
122 Remove everything in body before a scissors line. A line that
\r
123 mainly consists of scissors (either ">8" or "8<") and perforation
\r
124 (dash "-") marks is called a scissors line, and is used to request
\r
125 the reader to cut the message at that line. If such a line
\r
126 appears in the body of the message before the patch, everything
\r
127 before it (including the scissors line itself) is ignored when
\r
128 this option is used.
\r
130 <simpara>This is useful if you want to begin your message in a discussion thread
\r
131 with comments and suggestions on the message you are responding to, and to
\r
132 conclude it with a patch submission, separating the discussion and the
\r
133 beginning of the proposed commit log message with a scissors line.</simpara>
\r
134 <simpara>This can enabled by default with the configuration option mailinfo.scissors.</simpara>
\r
143 Ignore scissors lines. Useful for overriding mailinfo.scissors settings.
\r
153 The commit log message extracted from e-mail, usually
\r
154 except the title line which comes from e-mail Subject.
\r
164 The patch extracted from e-mail.
\r
170 <simplesect id="_git">
\r
172 <simpara>Part of the <xref linkend="git(1)" /> suite</simpara>
\r