3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
7 .\" Source: Git 2.40.1.423.g2807bd2c10
10 .TH "GIT\-AM" "1" "04/25/2023" "Git 2\&.40\&.1\&.423\&.g2807bd" "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-am \- Apply a series of patches from a mailbox
35 \fIgit am\fR [\-\-signoff] [\-\-keep] [\-\-[no\-]keep\-cr] [\-\-[no\-]utf8] [\-\-no\-verify]
36 [\-\-[no\-]3way] [\-\-interactive] [\-\-committer\-date\-is\-author\-date]
37 [\-\-ignore\-date] [\-\-ignore\-space\-change | \-\-ignore\-whitespace]
38 [\-\-whitespace=<option>] [\-C<n>] [\-p<n>] [\-\-directory=<dir>]
39 [\-\-exclude=<path>] [\-\-include=<path>] [\-\-reject] [\-q | \-\-quiet]
40 [\-\-[no\-]scissors] [\-S[<keyid>]] [\-\-patch\-format=<format>]
41 [\-\-quoted\-cr=<action>]
42 [\-\-empty=(stop|drop|keep)]
43 [(<mbox> | <Maildir>)\&...]
44 \fIgit am\fR (\-\-continue | \-\-skip | \-\-abort | \-\-quit | \-\-show\-current\-patch[=(diff|raw)] | \-\-allow\-empty)
49 Splits mail messages in a mailbox into commit log message, authorship information and patches, and applies them to the current branch\&. You could think of it as a reverse operation of \fBgit-format-patch\fR(1) run on a branch with a straight history without merges\&.
52 (<mbox>|<Maildir>)\&...
54 The list of mailbox files to read patches from\&. If you do not supply this argument, the command reads from the standard input\&. If you supply directories, they will be treated as Maildirs\&.
61 trailer to the commit message, using the committer identity of yourself\&. See the signoff option in
63 for more information\&.
73 \fBgit-mailinfo\fR(1))\&.
83 \fBgit-mailinfo\fR(1))\&.
89 \fB\-\-keep\-cr\fR, call
92 \fBgit-mailsplit\fR(1)) with the same option, to prevent it from stripping CR at the end of lines\&.
94 configuration variable can be used to specify the default behaviour\&.
95 \fB\-\-no\-keep\-cr\fR
102 Remove everything in body before a scissors line (see
103 \fBgit-mailinfo\fR(1))\&. Can be activated by default using the
104 \fBmailinfo\&.scissors\fR
105 configuration variable\&.
110 Ignore scissors lines (see
111 \fBgit-mailinfo\fR(1))\&.
114 \-\-quoted\-cr=<action>
116 This flag will be passed down to
119 \fBgit-mailinfo\fR(1))\&.
122 \-\-empty=(stop|drop|keep)
124 By default, or when the option is set to
125 \fIstop\fR, the command errors out on an input e\-mail message lacking a patch and stops into the middle of the current am session\&. When this option is set to
126 \fIdrop\fR, skip such an e\-mail message instead\&. When this option is set to
127 \fIkeep\fR, create an empty commit, recording the contents of the e\-mail message as its log\&.
137 \fBgit-mailinfo\fR(1)), so that the Message\-ID header is added to the commit message\&. The
139 configuration variable can be used to specify the default behaviour\&.
144 Do not add the Message\-ID header to the commit message\&.
145 \fBno\-message\-id\fR
146 is useful to override
147 \fBam\&.messageid\fR\&.
152 Be quiet\&. Only print error messages\&.
162 \fBgit-mailinfo\fR(1))\&. The proposed commit log message taken from the e\-mail is re\-coded into UTF\-8 encoding (configuration variable
163 \fBi18n\&.commitEncoding\fR
164 can be used to specify project\(cqs preferred encoding if it is not UTF\-8)\&.
166 This was optional in prior versions of git, but now it is the default\&. You can use
178 \fBgit-mailinfo\fR(1))\&.
181 \-3, \-\-3way, \-\-no\-3way
183 When the patch does not apply cleanly, fall back on 3\-way merge if the patch records the identity of blobs it is supposed to apply to and we have those blobs available locally\&.
185 can be used to override am\&.threeWay configuration variable\&. For more information, see am\&.threeWay in
186 \fBgit-config\fR(1)\&.
189 \-\-rerere\-autoupdate, \-\-no\-rerere\-autoupdate
191 After the rerere mechanism reuses a recorded resolution on the current conflict to update the files in the working tree, allow it to also update the index with the result of resolution\&.
192 \fB\-\-no\-rerere\-autoupdate\fR
193 is a good way to double\-check what
195 did and catch potential mismerges, before committing the result to the index with a separate
199 \-\-ignore\-space\-change, \-\-ignore\-whitespace, \-\-whitespace=<option>, \-C<n>, \-p<n>, \-\-directory=<dir>, \-\-exclude=<path>, \-\-include=<path>, \-\-reject
201 These flags are passed to the
204 \fBgit-apply\fR(1)) program that applies the patch\&.
209 By default the command will try to detect the patch format automatically\&. This option allows the user to bypass the automatic detection and specify the patch format that the patch(es) should be interpreted as\&. Valid formats are mbox, mboxrd, stgit, stgit\-series and hg\&.
219 By default, the pre\-applypatch and applypatch\-msg hooks are run\&. When any of
223 is given, these are bypassed\&. See also
227 \-\-committer\-date\-is\-author\-date
229 By default the command records the date from the e\-mail message as the commit author date, and uses the time of commit creation as the committer date\&. This allows the user to lie about the committer date by using the same value as the author date\&.
234 By default the command records the date from the e\-mail message as the commit author date, and uses the time of commit creation as the committer date\&. This allows the user to lie about the author date by using the same value as the committer date\&.
239 Skip the current patch\&. This is only meaningful when restarting an aborted patch\&.
242 \-S[<keyid>], \-\-gpg\-sign[=<keyid>], \-\-no\-gpg\-sign
244 GPG\-sign commits\&. The
246 argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space\&.
247 \fB\-\-no\-gpg\-sign\fR
248 is useful to countermand both
249 \fBcommit\&.gpgSign\fR
250 configuration variable, and earlier
251 \fB\-\-gpg\-sign\fR\&.
254 \-\-continue, \-r, \-\-resolved
256 After a patch failure (e\&.g\&. attempting to apply conflicting patch), the user has applied it by hand and the index file stores the result of the application\&. Make a commit using the authorship and commit log extracted from the e\-mail message and the current index file, and continue\&.
261 When a patch failure occurs, <msg> will be printed to the screen before exiting\&. This overrides the standard message informing you to use
265 to handle the failure\&. This is solely for internal use between
273 Restore the original branch and abort the patching operation\&. Revert contents of files involved in the am operation to their pre\-am state\&.
278 Abort the patching operation but keep HEAD and the index untouched\&.
281 \-\-show\-current\-patch[=(diff|raw)]
283 Show the message at which
285 has stopped due to conflicts\&. If
287 is specified, show the raw contents of the e\-mail message; if
288 \fBdiff\fR, show the diff portion only\&. Defaults to
294 After a patch failure on an input e\-mail message lacking a patch, create an empty commit with the contents of the e\-mail message as its log message\&.
298 The commit author name is taken from the "From: " line of the message, and commit author date is taken from the "Date: " line of the message\&. The "Subject: " line is used as the title of the commit, after stripping common prefix "[PATCH <anything>]"\&. The "Subject: " line is supposed to concisely describe what the commit is about in one line of text\&.
300 "From: ", "Date: ", and "Subject: " lines starting the body override the respective commit author name and title values taken from the headers\&.
302 The commit message is formed by the title taken from the "Subject: ", a blank line and the body of the message up to where the patch begins\&. Excess whitespace at the end of each line is automatically stripped\&.
304 The patch is expected to be inline, directly following the message\&. Any line that is of the form:
314 three\-dashes and end\-of\-line, or
325 a line that begins with "diff \-", or
336 a line that begins with "Index: "
339 is taken as the beginning of a patch, and the commit log message is terminated before the first occurrence of such a line\&.
341 When initially invoking \fBgit am\fR, you give it the names of the mailboxes to process\&. Upon seeing the first patch that does not apply, it aborts in the middle\&. You can recover from this in one of two ways:
351 skip the current patch by re\-running the command with the
364 hand resolve the conflict in the working directory, and update the index file to bring it into a state that the patch should have produced\&. Then run the command with the
369 The command refuses to process new mailboxes until the current operation is finished, so if you decide to start over from scratch, run \fBgit am \-\-abort\fR before running the command with mailbox names\&.
371 Before any patches are applied, ORIG_HEAD is set to the tip of the current branch\&. This is useful if you have problems with multiple commits, like running \fIgit am\fR on the wrong branch or an error in the commits that is more easily fixed by changing the mailbox (e\&.g\&. errors in the "From:" lines)\&.
374 This command can run \fBapplypatch\-msg\fR, \fBpre\-applypatch\fR, and \fBpost\-applypatch\fR hooks\&. See \fBgithooks\fR(5) for more information\&.
377 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:
381 If true, git\-am will call git\-mailsplit for patches in mbox format with parameter
382 \fB\-\-keep\-cr\fR\&. In this case git\-mailsplit will not remove
384 from lines ending with
385 \fB\er\en\fR\&. Can be overridden by giving
386 \fB\-\-no\-keep\-cr\fR
387 from the command line\&. See
389 \fBgit-mailsplit\fR(1)\&.
396 will fail if the patch does not apply cleanly\&. When set to true, this setting tells
398 to fall back on 3\-way merge if the patch records the identity of blobs it is supposed to apply to and we have those blobs available locally (equivalent to giving the
400 option from the command line)\&. Defaults to
406 \fBgit-apply\fR(1), \fBgit-format-patch\fR(1)\&.
409 Part of the \fBgit\fR(1) suite