Linux Documentation
 help / color / mirror / Atom feed
From: "Drew DeVault" <sir@cmpwn.com>
To: "Randy Dunlap" <rdunlap@infradead.org>,
	<linux-doc@vger.kernel.org>, "Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH 2/4] Documentation/process: expand plain-text advice
Date: Wed, 02 Sep 2020 12:20:43 -0400	[thread overview]
Message-ID: <C5D0R4LY727O.3IVTS5J20WHXW@homura> (raw)
In-Reply-To: <022eb995-5d47-c564-af55-239d5c3ab848@infradead.org>

On Wed Sep 2, 2020 at 12:06 PM EDT, Randy Dunlap wrote:
> On 9/2/20 8:57 AM, Drew DeVault wrote:
> > This adds a link to https://useplaintext.email to email-clients.rst,
> > which is a more exhaustive resource on configuring various mail clients
> > for plain text use. submitting-patches.rst is also updated to direct
> > readers to email-clients.rst to equip new contributors with the
> > requisite knowledge to become a good participant on the mailing lists.
> > 
> > Signed-off-by: Drew DeVault <sir@cmpwn.com>
> > ---
> > Conflict of interest: I wrote and maintain the website this links to.
> > 
> >  Documentation/process/email-clients.rst      | 5 +++++
> >  Documentation/process/submitting-patches.rst | 3 +++
> >  2 files changed, 8 insertions(+)
> > 
> > diff --git a/Documentation/process/email-clients.rst b/Documentation/process/email-clients.rst
> > index c9e4ce2613c0..16586f6cc888 100644
> > --- a/Documentation/process/email-clients.rst
> > +++ b/Documentation/process/email-clients.rst
> > @@ -25,6 +25,11 @@ attachments, but then the attachments should have content-type
> >  it makes quoting portions of the patch more difficult in the patch
> >  review process.
> >  
> > +It's also strongly recommended that you use plain text in your email body,
> > +for patches and other emails alike. https://useplaintext.email may be useful
>
> You could justify that first sentence by adding that some mailing
> lists drop/discard emails that are in html.

Will add this if the patch ends up being re-rolled, but I don't think it
necessarily warrants a v3.

  reply	other threads:[~2020-09-02 16:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 15:57 [PATCH 0/4] Improvements to submitting-patches.rst Drew DeVault
2020-09-02 15:57 ` [PATCH 1/4] submitting-patches.rst: remove heading numbering Drew DeVault
2020-09-03 15:44   ` Jonathan Corbet
2020-09-03 15:48     ` Drew DeVault
2020-09-03 15:46   ` Jonathan Corbet
2020-09-02 15:57 ` [PATCH 2/4] Documentation/process: expand plain-text advice Drew DeVault
2020-09-02 16:06   ` Randy Dunlap
2020-09-02 16:20     ` Drew DeVault [this message]
2020-09-03 15:47   ` Jonathan Corbet
2020-09-02 15:57 ` [PATCH 3/4] Documentation/maintainer: rehome sign-off process Drew DeVault
2020-09-03 15:50   ` Jonathan Corbet
2020-09-02 15:57 ` [PATCH 4/4] submitting-patches.rst: presume git will be used Drew DeVault
2020-09-02 16:11   ` Randy Dunlap
2020-09-02 16:11     ` Drew DeVault
2020-09-03 15:57   ` Jonathan Corbet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C5D0R4LY727O.3IVTS5J20WHXW@homura \
    --to=sir@cmpwn.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox