[1/3] doc: Point out preference of message format.
Commit Message
From 85c26ccbdedc55ca6490d4c2e0186e26672e3477 Mon Sep 17 00:00:00 2001
From: ng0 <ng0@we.make.ritual.n0.is>
Date: Thu, 21 Jul 2016 12:44:57 +0000
Subject: [PATCH 1/3] 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.
---
doc/contributing.texi | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.9.1
--
♥Ⓐ ng0 – http://we.make.ritual.n0.is
For non-prism friendly talk find me on http://www.psyced.org
SecuShare – http://secushare.org
Comments
ng0 <ng0@we.make.ritual.n0.is> skribis:
> From 85c26ccbdedc55ca6490d4c2e0186e26672e3477 Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@we.make.ritual.n0.is>
> Date: Thu, 21 Jul 2016 12:44:57 +0000
> Subject: [PATCH 1/3] 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.
Applied, thanks!
@@ -327,4 +327,7 @@ extensions---or to the operating system kernel---e.g., reliance on
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.