|
|
GIT-MAILINFO(1) Git Manual GIT-MAILINFO(1)
git-mailinfo - Extracts patch and authorship from a single e-mail
message
git mailinfo [-k|-b] [-u | --encoding=<encoding> | -n] [--[no-]scissors] <msg> <patch>
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 git am to create a commit. It is
usually not necessary to use this command directly. See git-am(1)
instead.
-k
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 git format-patch -k output.
Specifically, the following are removed until none of them
remain:
· Leading and trailing whitespace.
· Leading Re:, re:, and :.
· Leading bracketed strings (between [ and ], usually [PATCH]).
Finally, runs of whitespace are normalized to a single ASCII
space character.
-b
When -k is not in effect, all leading strings bracketed with [
and ] pairs are stripped. This option limits the stripping to
only the pairs whose bracketed string contains the word "PATCH".
-u
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
i18n.commitencoding (defaulting to UTF-8) by transliterating
them. This used to be optional but now it is the default.
Note that the patch is always used as-is without charset
conversion, even with this flag.
--encoding=<encoding>
Similar to -u. But when re-coding, the charset specified here is
used instead of the one specified by i18n.commitencoding or
UTF-8.
-n
Disable all charset re-coding of the metadata.
-m, --message-id
Copy the Message-ID header at the end of the commit message. This
is useful in order to associate commits with mailing list
discussions.
--scissors
Remove everything in body before a scissors line. A line that
mainly consists of scissors (either ">8" or "8<") and perforation
(dash "-") marks is called a scissors line, and is used to
request the reader to cut the message at that line. If such a
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.
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.
This can be enabled by default with the configuration option
mailinfo.scissors.
--no-scissors
Ignore scissors lines. Useful for overriding mailinfo.scissors
settings.
<msg>
The commit log message extracted from e-mail, usually except the
title line which comes from e-mail Subject.
<patch>
The patch extracted from e-mail.
Part of the git(1) suite
This page is part of the git (Git distributed version control system)
project. Information about the project can be found at
⟨http://git-scm.com/⟩. If you have a bug report for this manual page,
see ⟨http://git-scm.com/community⟩. This page was obtained from the
project's upstream Git repository ⟨https://github.com/git/git.git⟩ on
2018-02-02. (At that time, the date of the most recent commit that
was found in the repository was 2018-01-23.) If you discover any
rendering problems in this HTML version of the page, or you believe
there is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
man-pages@man7.org
Git 2.9.2.277.g2949358 07/16/2016 GIT-MAILINFO(1)
Pages that refer to this page: git(1), git-am(1), git-config(1)
|
HTML rendering created 2018-02-02 by Michael Kerrisk, author of The Linux Programming Interface, maintainer of the Linux man-pages project. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH.
|
|