undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: minor grammatical fixes.

Browse Source 
Signed-off-by: David J. Mellor <dmellor@whistlingcat.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
David J. Mellor 2009-03-01 22:37:41 -08:00 committed by Junio C Hamano
parent 2559bff32c
commit 07f5746fb5
1 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
Documentation/git-am.txt
View File

@ -27,8 +27,8 @@ OPTIONS
------- -------
<mbox>|<Maildir>...:: <mbox>|<Maildir>...::
The list of mailbox files to read patches from. If you do not The list of mailbox files to read patches from. If you do not
supply this argument, reads from the standard input. If you supply supply this argument, the command reads from the standard input.
directories, they'll be treated as Maildirs. If you supply directories, they will be treated as Maildirs.
-s:: -s::
--signoff:: --signoff::
@ -48,7 +48,7 @@ OPTIONS
preferred encoding if it is not UTF-8). preferred encoding if it is not UTF-8).
+ +
This was optional in prior versions of git, but now it is the This was optional in prior versions of git, but now it is the
default. You could use `--no-utf8` to override this. default. You can use `--no-utf8` to override this.
--no-utf8:: --no-utf8::
Pass `-n` flag to 'git-mailinfo' (see Pass `-n` flag to 'git-mailinfo' (see
@ -57,8 +57,8 @@ default. You could use `--no-utf8` to override this.
-3:: -3::
--3way:: --3way::
When the patch does not apply cleanly, fall back on When the patch does not apply cleanly, fall back on
3-way merge, if the patch records the identity of blobs 3-way merge if the patch records the identity of blobs
it is supposed to apply to, and we have those blobs it is supposed to apply to and we have those blobs
available locally. available locally.
--whitespace=<option>:: --whitespace=<option>::
@ -121,18 +121,18 @@ the commit, after stripping common prefix "[PATCH <anything>]".
It is supposed to describe what the commit is about concisely as It is supposed to describe what the commit is about concisely as
a one line text. a one line text.
The body of the message (iow, after a blank line that terminates The body of the message (the rest of the message after the blank line
RFC2822 headers) can begin with "Subject: " and "From: " lines that terminates the RFC2822 headers) can begin with "Subject: " and
that are different from those of the mail header, to override "From: " lines that are different from those of the mail header,
the values of these fields. to override the values of these fields.
The commit message is formed by the title taken from the The commit message is formed by the title taken from the
"Subject: ", a blank line and the body of the message up to "Subject: ", a blank line and the body of the message up to
where the patch begins. Excess whitespaces at the end of the where the patch begins. Excess whitespace characters at the end of the
lines are automatically stripped. lines are automatically stripped.
The patch is expected to be inline, directly following the The patch is expected to be inline, directly following the
message. Any line that is of form: message. Any line that is of the form:
* three-dashes and end-of-line, or * three-dashes and end-of-line, or
* a line that begins with "diff -", or * a line that begins with "diff -", or
@ -141,18 +141,18 @@ message. Any line that is of form:
is taken as the beginning of a patch, and the commit log message is taken as the beginning of a patch, and the commit log message
is terminated before the first occurrence of such a line. is terminated before the first occurrence of such a line.
When initially invoking it, you give it names of the mailboxes When initially invoking it, you give it the names of the mailboxes
to crunch. Upon seeing the first patch that does not apply, it 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: aborts in the middle. You can recover from this in one of two ways:
. skip the current patch by re-running the command with '--skip' . skip the current patch by re-running the command with the '--skip'
option. option.
. hand resolve the conflict in the working directory, and update . hand resolve the conflict in the working directory, and update
the index file to bring it in a state that the patch should the index file to bring it into a state that the patch should
have produced. Then run the command with '--resolved' option. have produced. Then run the command with the '--resolved' option.
The command refuses to process new mailboxes while `.git/rebase-apply` The command refuses to process new mailboxes while the `.git/rebase-apply`
directory exists, so if you decide to start over from scratch, directory exists, so if you decide to start over from scratch,
run `rm -f -r .git/rebase-apply` before running the command with mailbox run `rm -f -r .git/rebase-apply` before running the command with mailbox
names. names.