write in 30M

hc

2024-02-20 ea08eeccae9297f7aabd2ef7f0c2517ac4549acc

 kernel/Documentation/process/email-clients.rst
..
..
@@ -25,6 +25,11 @@
25
25
 it makes quoting portions of the patch more difficult in the patch
26
26
 review process.
27
27
 
28
+It's also strongly recommended that you use plain text in your email body,
29
+for patches and other emails alike. https://useplaintext.email may be useful
30
+for information on how to configure your preferred email client, as well as
31
+listing recommended email clients should you not already have a preference.
32
+
28
33
 Email clients that are used for Linux kernel patches should send the
29
34
 patch text untouched.  For example, they should not modify or delete tabs
30
35
 or spaces, even at the beginning or end of lines.
..
..
@@ -40,7 +45,7 @@
40
45
 If you configure your email client to send emails with UTF-8 encoding,
41
46
 you avoid some possible charset problems.
42
47
 
43
-Email clients should generate and maintain References: or In-Reply-To:
48
+Email clients should generate and maintain "References:" or "In-Reply-To:"
44
49
 headers so that mail threading is not broken.
45
50
 
46
51
 Copy-and-paste (or cut-and-paste) usually does not work for patches
..
..
@@ -89,7 +94,7 @@
89
94
 
90
95
 Works. Some people use this successfully for patches.
91
96
 
92
-To insert a patch use :menuselection:`Message-->Insert` File (:kbd:`CTRL-I`)
97
+To insert a patch use :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`)
93
98
 or an external editor.
94
99
 
95
100
 If the inserted patch has to be edited in the Claws composition window
..
..
@@ -132,8 +137,8 @@
132
137
 At the bottom of your email, put the commonly-used patch delimiter before
133
138
 inserting your patch:  three hyphens (``---``).
134
139
 
135
-Then from the :menuselection:`Message` menu item, select insert file and
136
-choose your patch.
140
+Then from the :menuselection:`Message` menu item, select
141
+:menuselection:`insert file` and choose your patch.
137
142
 As an added bonus you can customise the message creation toolbar menu
138
143
 and put the :menuselection:`insert file` icon there.
139
144
 
..
..
@@ -149,18 +154,16 @@
149
154
 as inlined text will make them tricky to extract from their 7-bit encoding.
150
155
 
151
156
 If you absolutely must send patches as attachments instead of inlining
152
-them as text, right click on the attachment and select properties, and
153
-highlight :menuselection:`Suggest automatic display` to make the attachment
157
+them as text, right click on the attachment and select :menuselection:`properties`,
158
+and highlight :menuselection:`Suggest automatic display` to make the attachment
154
159
 inlined to make it more viewable.
155
160
 
156
161
 When saving patches that are sent as inlined text, select the email that
157
162
 contains the patch from the message list pane, right click and select
158
163
 :menuselection:`save as`.  You can use the whole email unmodified as a patch
159
-if it was properly composed.  There is no option currently to save the email
160
-when you are actually viewing it in its own window -- there has been a request
161
-filed at kmail's bugzilla and hopefully this will be addressed.  Emails are
162
-saved as read-write for user only so you will have to chmod them to make them
163
-group and world readable if you copy them elsewhere.
164
+if it was properly composed.  Emails are saved as read-write for user only so
165
+you will have to chmod them to make them group and world readable if you copy
166
+them elsewhere.
164
167
 
165
168
 Lotus Notes (GUI)
166
169
 *****************
..
..
@@ -239,9 +242,9 @@
239
242
 
240
243
 The Mutt docs have lots more information:
241
244
 
242
-    http://dev.mutt.org/trac/wiki/UseCases/Gmail
245
+    https://gitlab.com/muttmua/mutt/-/wikis/UseCases/Gmail
243
246
 
244
-    http://dev.mutt.org/doc/manual.html
247
+    http://www.mutt.org/doc/manual/
245
248
 
246
249
 Pine (TUI)
247
250
 **********