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.47.0.305.g4083a6f052
10 .TH "GIT\-AM" "1" "2024-11-20" "Git 2\&.47\&.0\&.305\&.g4083a6" "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=<action>] [\-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 | \-\-retry | \-\-show\-current\-patch[=(diff|raw)] | \-\-allow\-empty)
48 Splits mail messages in a mailbox into commit log messages, 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\&.
51 (<mbox>|<Maildir>)\&...\:
53 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\&.
60 trailer to the commit message, using the committer identity of yourself\&. See the signoff option in
62 for more information\&.
72 \fBgit-mailinfo\fR(1))\&.
82 \fBgit-mailinfo\fR(1))\&.
88 \fB\-\-keep\-cr\fR, call
91 \fBgit-mailsplit\fR(1)) with the same option, to prevent it from stripping CR at the end of lines\&.
93 configuration variable can be used to specify the default behaviour\&.
94 \fB\-\-no\-keep\-cr\fR
101 Remove everything in body before a scissors line (see
102 \fBgit-mailinfo\fR(1))\&. Can be activated by default using the
103 \fBmailinfo\&.scissors\fR
104 configuration variable\&.
109 Ignore scissors lines (see
110 \fBgit-mailinfo\fR(1))\&.
113 \-\-quoted\-cr=<action>
115 This flag will be passed down to
118 \fBgit-mailinfo\fR(1))\&.
121 \-\-empty=(drop|keep|stop)
123 How to handle an e\-mail message lacking a patch:
127 The e\-mail message will be skipped\&.
132 An empty commit will be created, with the contents of the e\-mail message as its log\&.
137 The command will fail, stopping in the middle of the current
139 session\&. This is the default behavior\&.
150 \fBgit-mailinfo\fR(1)), so that the Message\-ID header is added to the commit message\&. The
152 configuration variable can be used to specify the default behaviour\&.
157 Do not add the Message\-ID header to the commit message\&.
158 \fBno\-message\-id\fR
159 is useful to override
160 \fBam\&.messageid\fR\&.
165 Be quiet\&. Only print error messages\&.
175 \fBgit-mailinfo\fR(1))\&. The proposed commit log message taken from the e\-mail is re\-coded into UTF\-8 encoding (configuration variable
176 \fBi18n\&.commitEncoding\fR
177 can be used to specify the project\(cqs preferred encoding if it is not UTF\-8)\&.
179 This was optional in prior versions of git, but now it is the default\&. You can use
191 \fBgit-mailinfo\fR(1))\&.
194 \-3, \-\-3way, \-\-no\-3way
196 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\&.
198 can be used to override am\&.threeWay configuration variable\&. For more information, see am\&.threeWay in
199 \fBgit-config\fR(1)\&.
202 \-\-rerere\-autoupdate, \-\-no\-rerere\-autoupdate
204 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\&.
205 \fB\-\-no\-rerere\-autoupdate\fR
206 is a good way to double\-check what
208 did and catch potential mismerges, before committing the result to the index with a separate
213 \-\-ignore\-space\-change, \-\-ignore\-whitespace, \-\-whitespace=<action>, \-C<n>, \-p<n>, \-\-directory=<dir>, \-\-exclude=<path>, \-\-include=<path>, \-\-reject
215 These flags are passed to the
218 \fBgit-apply\fR(1)) program that applies the patch\&.
220 Valid <action> for the
232 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\&.
242 By default, the pre\-applypatch and applypatch\-msg hooks are run\&. When any of
246 is given, these are bypassed\&. See also
250 \-\-committer\-date\-is\-author\-date
252 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\&.
257 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\&.
262 Skip the current patch\&. This is only meaningful when restarting an aborted patch\&.
265 \-S[<keyid>], \-\-gpg\-sign[=<keyid>], \-\-no\-gpg\-sign
267 GPG\-sign commits\&. The
269 argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space\&.
270 \fB\-\-no\-gpg\-sign\fR
271 is useful to countermand both
272 \fBcommit\&.gpgSign\fR
273 configuration variable, and earlier
274 \fB\-\-gpg\-sign\fR\&.
277 \-\-continue, \-r, \-\-resolved
279 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\&.
284 When a patch failure occurs, <msg> will be printed to the screen before exiting\&. This overrides the standard message informing you to use
288 to handle the failure\&. This is solely for internal use between
296 Restore the original branch and abort the patching operation\&. Revert the contents of files involved in the am operation to their pre\-am state\&.
301 Abort the patching operation but keep HEAD and the index untouched\&.
306 Try to apply the last conflicting patch again\&. This is generally only useful for passing extra options to the retry attempt (e\&.g\&.,
307 \fB\-\-3way\fR), since otherwise you\(cqll just see the same failure again\&.
310 \-\-show\-current\-patch[=(diff|raw)]
312 Show the message at which
315 has stopped due to conflicts\&. If
317 is specified, show the raw contents of the e\-mail message; if
318 \fBdiff\fR, show the diff portion only\&. Defaults to
324 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\&.
328 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\&.
330 "From: ", "Date: ", and "Subject: " lines starting the body override the respective commit author name and title values taken from the headers\&.
332 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\&.
334 The patch is expected to be inline, directly following the message\&. Any line that is of the form:
344 three\-dashes and end\-of\-line, or
355 a line that begins with "diff \-", or
366 a line that begins with "Index: "
369 is taken as the beginning of a patch, and the commit log message is terminated before the first occurrence of such a line\&.
371 When initially invoking \fBgit\fR \fBam\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:
381 skip the current patch by re\-running the command with the
394 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
399 The command refuses to process new mailboxes until the current operation is finished, so if you decide to start over from scratch, run \fBgit\fR \fBam\fR \fB\-\-abort\fR before running the command with mailbox names\&.
401 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)\&.
404 This command can run \fBapplypatch\-msg\fR, \fBpre\-applypatch\fR, and \fBpost\-applypatch\fR hooks\&. See \fBgithooks\fR(5) for more information\&.
407 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:
411 If true, git\-am will call git\-mailsplit for patches in mbox format with parameter
412 \fB\-\-keep\-cr\fR\&. In this case git\-mailsplit will not remove \er from lines ending with \er\en\&. Can be overridden by giving
413 \fB\-\-no\-keep\-cr\fR
414 from the command line\&. See
416 \fBgit-mailsplit\fR(1)\&.
424 will fail if the patch does not apply cleanly\&. When set to true, this setting tells
427 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
429 option from the command line)\&. Defaults to
435 \fBgit-apply\fR(1), \fBgit-format-patch\fR(1)\&.
438 Part of the \fBgit\fR(1) suite