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 D4458D1E for ; Tue, 18 Sep 2018 16:32:52 +0000 (UTC) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8652242D for ; Tue, 18 Sep 2018 16:32:52 +0000 (UTC) Date: Tue, 18 Sep 2018 09:32:34 -0700 From: "Luck, Tony" To: Mark Brown Message-ID: <20180918163231.GB10134@agluck-desk> References: <20180917115916.37fd5388@coco.lan> <2174637.IVJC5EhCEq@avalon> <20180918160236.GK2471@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180918160236.GK2471@sirena.org.uk> Cc: mchehab+samsung@kernel.org, Tim Bird , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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. -Tony