Thread (42 messages) 42 messages, 5 authors, 2023-12-28
DORMANTno replies
Revisions (2)
  1. v2 [diff vs current]
  2. v3 current

[PATCH v3 9/9] SubmittingPatches: hyphenate non-ASCII

From: Josh Soref via GitGitGadget <hidden>
Date: 2023-12-28 04:55:37
Subsystem: documentation, the rest · Maintainers: Jonathan Corbet, Linus Torvalds

From: Josh Soref <redacted>

Git documentation does this with the exception of ancient release notes.

Signed-off-by: Josh Soref <redacted>
---
 Documentation/SubmittingPatches | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 5e2e13b5e09..e734a3f0f17 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -699,7 +699,7 @@ message to an external program, and this is a handy way to drive
 `git am`.  However, if the message is MIME encoded, what is
 piped into the program is the representation you see in your
 `*Article*` buffer after unwrapping MIME.  This is often not what
-you would want for two reasons.  It tends to screw up non ASCII
+you would want for two reasons.  It tends to screw up non-ASCII
 characters (most notably in people's names), and also
 whitespaces (fatal in patches).  Running "C-u g" to display the
 message in raw form before using "|" to run the pipe can work
-- 
gitgitgadget
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help