aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorng0 <ng0@we.make.ritual.n0.is>2016-07-21 12:44:57 +0000
committerLudovic Courtès <ludo@gnu.org>2016-07-24 19:54:15 +0200
commit0f53b886e27ac6ea340d19f3627c273c7f82016e (patch)
treef42a39d652a65182bd47df4639d10a4b622ac346
parentdfcdd9c25d552fb2691552837b2f2f50bb0b14fb (diff)
downloadpatches-0f53b886e27ac6ea340d19f3627c273c7f82016e.tar
patches-0f53b886e27ac6ea340d19f3627c273c7f82016e.tar.gz
doc: Point out preference of message format.
* doc/contributing.texi (Submitting Patches): Includes a note on preference of plain text messages with either inline or MIME attachments and advise contributers to pay attention if their email client breaks the patches. Signed-off-by: Ludovic Courtès <ludo@gnu.org>
-rw-r--r--doc/contributing.texi5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/contributing.texi b/doc/contributing.texi
index c8f884eacd..c0755bb895 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -337,4 +337,7 @@ referring to people, such as
When posting a patch to the mailing list, use @samp{[PATCH] @dots{}} as
a subject. You may use your email client or the @command{git
-send-email} command.
+send-email} command. We prefer to get patches in plain text messages,
+either inline or as MIME attachments. You are advised to pay attention if
+your email client changes anything like line breaks or indentation which
+could could potentially break the patches.