public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Conor Dooley <conor@kernel.org>
Cc: corbet@lwn.net, Conor Dooley <conor.dooley@microchip.com>,
	broonie@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Documentation: process: Document suitability of Proton Mail for kernel development
Date: Fri, 30 Dec 2022 14:43:22 -0500	[thread overview]
Message-ID: <20221230194322.gonid4ld27jwjfw4@nitro.local> (raw)
In-Reply-To: <20221228000330.3971104-1-conor@kernel.org>

On Wed, Dec 28, 2022 at 12:03:31AM +0000, Conor Dooley wrote:
> +This affects mail sent from their web GUI, from other mail clients using their
> +mail "bridge", as well as patches sent using ``git send-email``.

I suggest a minor tweak to wording here:

    The automatic encryption feature is also enabled for mail sent via the
    Proton Mail Bridge, so this affects all outgoing messages, including
    patches sent with ``git send-email``.

> +Unless a way to disable this "feature" is introduced, Proton Mail is unsuited
> +to kernel development.

Reviewed-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>

Thanks!

-K

      parent reply	other threads:[~2022-12-30 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  0:03 [PATCH v1] Documentation: process: Document suitability of Proton Mail for kernel development Conor Dooley
2022-12-28 12:33 ` Bagas Sanjaya
2022-12-28 13:06   ` Conor Dooley
2022-12-29 13:13 ` Mark Brown
2022-12-30 19:43 ` Konstantin Ryabitsev [this message]

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=20221230194322.gonid4ld27jwjfw4@nitro.local \
    --to=konstantin@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=conor@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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