From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 1710613D0 for ; Tue, 18 Sep 2018 21:01:51 +0000 (UTC) Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8BD7542D for ; Tue, 18 Sep 2018 21:01:50 +0000 (UTC) Date: Tue, 18 Sep 2018 17:01:47 -0400 From: Steven Rostedt To: Dmitry Torokhov Message-ID: <20180918170147.61fe4135@gandalf.local.home> In-Reply-To: References: <20180917115916.37fd5388@coco.lan> <2174637.IVJC5EhCEq@avalon> <20180918160236.GK2471@sirena.org.uk> <20180918163231.GB10134@agluck-desk> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Mauro Carvalho Chehab , tim.bird@sony.com, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 18 Sep 2018 09:35:28 -0700 Dmitry Torokhov wrote: > On Tue, Sep 18, 2018 at 9:33 AM Luck, Tony wrote: > > > > On Tue, Sep 18, 2018 at 09:02:36AM -0700, Mark Brown wrote: > > > At least with Outlook the problem is partly that Outlook's model of how > > > e-mail works isn't really able to cope with what we need, it translates > > > everything into internal formats in a way that is at best fragile for > > > what we need. > > > > Or, shock, horror, tell one-time contributors that it is OK to > > put the patch in an attachment to the e-mail. Outlook doesn't > > (usually) mess with the contents of attachments. > > And then have maintainer having hard time trying to comment on said > patch in the attachment. I'd rather not. > This is why I use claws-mail. One of the nice features to it, is if you receive a patch as an attachment, you open it up, select all the text (right-click->select all), and then hit "reply". It makes it just as if the patch was the email. Then you can easily make your inline comments as usual. -- Steve