Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.17.0 04/02/18
- 2.10.1 → 2.16.3 no changes
- 2.10.0 09/02/16
- 2.9.4 → 2.9.5 no changes
- 2.9.3 08/12/16
- 2.7.2 → 2.9.2 no changes
- 2.7.1 02/05/16
- 2.6.3 → 2.7.0 no changes
- 2.6.2 10/16/15
- 2.6.1 no changes
- 2.6.0 09/28/15
- 2.3.3 → 2.5.6 no changes
- 2.3.2 03/06/15
- 2.3.1 no changes
- 2.3.0 02/05/15
- 2.2.3 no changes
- 2.2.2 01/12/15
git am [--signoff] [--keep] [--utf8 | --no-utf8] [--3way] [--interactive] [--committer-date-is-author-date] [--ignore-date] [--ignore-space-change | --ignore-whitespace] [--whitespace=<option>] [-C<n>] [-p<n>] [--directory=<dir>] [--reject] [-q | --quiet] [--scissors | --no-scissors] [<mbox> | <Maildir>…] git am (--continue | --skip | --abort)
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-by:line to the commit message, using the committer identity of yourself.
-kflag to git mailinfo (see git-mailinfo).
Remove everything in body before a scissors line (see git-mailinfo).
Ignore scissors lines (see git-mailinfo).
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.
These flags are passed to the git apply (see git-apply) program that applies the patch.
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.
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.
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: " 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 --skip option.
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 --resolved option.
The command refuses to process new mailboxes while the
directory exists, so if you decide to start over from scratch,
rm -f -r .git/rebase-apply 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).
Written by Junio C Hamano <email@example.com>
Documentation by Petr Baudis, Junio C Hamano and the git-list <firstname.lastname@example.org>.
Part of the git suite