projects
/
linux.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
87eae26
)
docs: process: typo fix
author
Xujun Leng
<lengxujun2007@126.com>
Sun, 12 Mar 2023 07:14:23 +0000
(15:14 +0800)
committer
Jonathan Corbet
<corbet@lwn.net>
Tue, 14 Mar 2023 17:31:08 +0000
(11:31 -0600)
In the second paragraph of section "Respond to review comments", there is
a spelling mistake: "aganst" should be "against".
Signed-off-by: Xujun Leng <lengxujun2007@126.com>
Link:
https://lore.kernel.org/r/20230312071423.3042-1-lengxujun2007@126.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Documentation/process/submitting-patches.rst
patch
|
blob
|
history
diff --git
a/Documentation/process/submitting-patches.rst
b/Documentation/process/submitting-patches.rst
index eac7167dce83d0fd7665a874aceaa4c9fa5d9e83..69ce64e03c70f8e5ff39c951d28f3597f40a3bdd 100644
(file)
--- a/
Documentation/process/submitting-patches.rst
+++ b/
Documentation/process/submitting-patches.rst
@@
-320,7
+320,7
@@
for their time. Code review is a tiring and time-consuming process, and
reviewers sometimes get grumpy. Even in that case, though, respond
politely and address the problems they have pointed out. When sending a next
version, add a ``patch changelog`` to the cover letter or to individual patches
-explaining difference aganst previous submission (see
+explaining difference aga
i
nst previous submission (see
:ref:`the_canonical_patch_format`).
See Documentation/process/email-clients.rst for recommendations on email