Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- All guides...
- 2.38.1 no changes
- 2.38.0 10/02/22
- 2.35.1 → 2.37.4 no changes
- 2.35.0 01/24/22
- 2.33.2 → 2.34.5 no changes
- 2.33.1 10/12/21
- 2.32.1 → 2.33.0 no changes
- 2.32.0 06/06/21
- 2.31.1 → 2.31.5 no changes
- 2.31.0 03/15/21
- 2.30.1 → 2.30.6 no changes
- 2.30.0 12/27/20
- 2.27.1 → 2.29.3 no changes
- 2.27.0 06/01/20
- 2.26.1 → 2.26.3 no changes
- 2.26.0 03/22/20
- 2.25.1 → 2.25.5 no changes
- 2.25.0 01/13/20
- 2.22.1 → 2.24.4 no changes
- 2.22.0 06/07/19
git am [--signoff] [--keep] [--[no-]keep-cr] [--[no-]utf8] [--[no-]3way] [--interactive] [--committer-date-is-author-date] [--ignore-date] [--ignore-space-change | --ignore-whitespace] [--whitespace=<option>] [-C<n>] [-p<n>] [--directory=<dir>] [--exclude=<path>] [--include=<path>] [--reject] [-q | --quiet] [--[no-]scissors] [-S[<keyid>]] [--patch-format=<format>] [--quoted-cr=<action>] [--empty=(stop|drop|keep)] [(<mbox> | <Maildir>)…] git am (--continue | --skip | --abort | --quit | --show-current-patch[=(diff|raw)] | --allow-empty)
Splits mail messages in a mailbox into commit log message, authorship information and patches, and applies them to the current branch.
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.
Signed-off-bytrailer to the commit message, using the committer identity of yourself. See the signoff option in git-commit for more information.
-kflag to git mailinfo (see git-mailinfo).
-bflag to git mailinfo (see git-mailinfo).
--keep-cr, call git mailsplit (see git-mailsplit) with the same option, to prevent it from stripping CR at the end of lines.
am.keepcrconfiguration variable can be used to specify the default behaviour.
--no-keep-cris useful to override
Remove everything in body before a scissors line (see git-mailinfo). Can be activated by default using the
Ignore scissors lines (see git-mailinfo).
This flag will be passed down to git mailinfo (see git-mailinfo).
By default, or when the option is set to stop, 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 drop, skip such an e-mail message instead. When this option is set to keep, create an empty commit, recording the contents of the e-mail message as its log.
-mflag to git mailinfo (see git-mailinfo), so that the Message-ID header is added to the commit message. The
am.messageidconfiguration variable can be used to specify the default behaviour.
Do not add the Message-ID header to the commit message.
no-message-idis useful to override
Be quiet. Only print error messages.
-uflag to git mailinfo (see git-mailinfo). The proposed commit log message taken from the e-mail is re-coded into UTF-8 encoding (configuration variable
i18n.commitEncodingcan be used to specify project’s preferred encoding if it is not UTF-8).
This was optional in prior versions of git, but now it is the default. You can use
--no-utf8to override this.
-nflag to git mailinfo (see git-mailinfo).
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.
--no-3waycan be used to override am.threeWay configuration variable. For more information, see am.threeWay in git-config.
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.
--no-rerere-autoupdateis a good way to double-check what
rereredid and catch potential mismerges, before committing the result to the index with a separate
These flags are passed to the git apply (see git-apply) program that applies the patch.
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.
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.
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.
Skip the current patch. This is only meaningful when restarting an aborted patch.
GPG-sign commits. The
keyidargument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space.
--no-gpg-signis useful to countermand both
commit.gpgSignconfiguration variable, and earlier
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.
When a patch failure occurs, <msg> will be printed to the screen before exiting. This overrides the standard message informing you to use
--skipto handle the failure. This is solely for internal use between git rebase and git am.
Restore the original branch and abort the patching operation. Revert contents of files involved in the am operation to their pre-am state.
Abort the patching operation but keep HEAD and the index untouched.
Show the message at which
git amhas stopped due to conflicts. If
rawis specified, show the raw contents of the e-mail message; if
diff, show the diff portion only. Defaults to
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.
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.
"From: ", "Date: ", and "Subject: " lines starting the body override the respective commit author name and title values taken from the headers.
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.
The patch is expected to be inline, directly following the message. Any line that is of the form:
three-dashes and end-of-line, or
a line that begins with "diff -", or
a line that begins with "Index: "
is taken as the beginning of a patch, and the commit log message is terminated before the first occurrence of such a line.
When initially invoking
git am, 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:
skip the current patch by re-running the command with the
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
The command refuses to process new mailboxes until the current
operation is finished, so if you decide to start over from scratch,
git am --abort before running the command with mailbox
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 git am 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).
This command can run
post-applypatch hooks. See githooks for more
Everything below this line in this section is selectively included from the git-config documentation. The content is the same as what’s found there:
If true, git-am will call git-mailsplit for patches in mbox format with parameter
--keep-cr. In this case git-mailsplit will not remove
\rfrom lines ending with
\r\n. Can be overridden by giving
--no-keep-crfrom the command line. See git-am, git-mailsplit.
git amwill fail if the patch does not apply cleanly. When set to true, this setting tells
git amto 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
--3wayoption from the command line). Defaults to
false. See git-am.
Part of the git suite