Documentation/SubmittingPatches: Gnus tips
Also warn about format=flowed (aka 'flawed'). Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Jan 17, 2007 at 01:07 UTC
e30b217ba41081f5f11206ca3dfb987725315304
1 file changed
+19
-1
Documentation/SubmittingPatches
+19
-1
@@ -72,7 +72,9 @@ other than the commit message itself. Place such "cover letter"
72
material between the three dash lines and the diffstat.
73
74
Do not attach the patch as a MIME attachment, compressed or not.
75
-Do not let your e-mail client send quoted-printable. Many
75
+Do not let your e-mail client send quoted-printable. Do not let
76
+your e-mail client send format=flowed which would destroy
77
+whitespaces in your patches. Many
78
popular e-mail applications will not always transmit a MIME
79
attachment as plain text, making it impossible to comment on
80
your code. A MIME attachment also takes a bit more time to
@@ -312,3 +314,19 @@ settings but I haven't tried, yet.
314
mail.identity.default.compose_html => false
315
mail.identity.id?.compose_html => false
316
317
+
318
+
319
+Gnus
320
+----
321
+
322
+'|' in the *Summary* buffer can be used to pipe the current
323
+message to an external program, and this is a handy way to drive
324
+"git am". However, if the message is MIME encoded, what is
325
+piped into the program is the representation you see in your
326
+*Article* buffer after unwrapping MIME. This is often not what
327
+you would want for two reasons. It tends to screw up non ASCII
328
+characters (most notably in people's names), and also
329
+whitespaces (fatal in patches). Running 'C-u g' to display the
330
+message in raw form before using '|' to run the pipe can work
331
+this problem around.
332
+