Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 30 Dec 2022 14:43:22 -0500
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
Message-ID: <20221230194322.gonid4ld27jwjfw4@nitro.local>
References: <20221228000330.3971104-1-conor@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20221228000330.3971104-1-conor@kernel.org>
Precedence: bulk

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