@@ -32,7 +32,7 @@ OPTIONS
32
32
33
33
-s::
34
34
--signoff::
35
- Add `Signed-off-by:` line to the commit message, using
35
+ Add a `Signed-off-by:` line to the commit message, using
36
36
the committer identity of yourself.
37
37
38
38
-k::
@@ -79,14 +79,14 @@ default. You can use `--no-utf8` to override this.
79
79
message as the commit author date, and uses the time of
80
80
commit creation as the committer date. This allows the
81
81
user to lie about the committer date by using the same
82
- timestamp as the author date.
82
+ value as the author date.
83
83
84
84
--ignore-date::
85
85
By default the command records the date from the e-mail
86
86
message as the commit author date, and uses the time of
87
87
commit creation as the committer date. This allows the
88
- user to lie about author timestamp by using the same
89
- timestamp as the committer date.
88
+ user to lie about the author date by using the same
89
+ value as the committer date.
90
90
91
91
--skip::
92
92
Skip the current patch. This is only meaningful when
@@ -115,21 +115,21 @@ DISCUSSION
115
115
----------
116
116
117
117
The commit author name is taken from the "From: " line of the
118
- message, and commit author time is taken from the "Date: " line
118
+ message, and commit author date is taken from the "Date: " line
119
119
of the message. The "Subject: " line is used as the title of
120
120
the commit, after stripping common prefix "[PATCH <anything>]".
121
- It is supposed to describe what the commit is about concisely as
122
- a one line text.
121
+ The "Subject: " line is supposed to concisely describe what the
122
+ commit is about in one line of text.
123
123
124
- The body of the message (the rest of the message after the blank line
125
- that terminates the RFC2822 headers) can begin with "Subject: " and
126
- "From: " lines that are different from those of the mail header,
127
- to override the values of these fields .
124
+ "From: " and "Subject: " lines starting the body (the rest of the
125
+ message after the blank line terminating the RFC2822 headers)
126
+ override the respective commit author name and title values taken
127
+ from the headers .
128
128
129
129
The commit message is formed by the title taken from the
130
130
"Subject: ", a blank line and the body of the message up to
131
- where the patch begins. Excess whitespace characters at the end of the
132
- lines are automatically stripped.
131
+ where the patch begins. Excess whitespace at the end of each
132
+ line is automatically stripped.
133
133
134
134
The patch is expected to be inline, directly following the
135
135
message. Any line that is of the form:
@@ -141,7 +141,7 @@ message. Any line that is of the form:
141
141
is taken as the beginning of a patch, and the commit log message
142
142
is terminated before the first occurrence of such a line.
143
143
144
- When initially invoking it , you give it the names of the mailboxes
144
+ When initially invoking `git am` , you give it the names of the mailboxes
145
145
to process. Upon seeing the first patch that does not apply, it
146
146
aborts in the middle. You can recover from this in one of two ways:
147
147
0 commit comments