Received-SPF: pass (google.com: domain of linux-kernel+bounces-161439-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Message-ID: <ee12e2f4-3e43-406b-816a-5f5822002f39@gmail.com>
Date: Sun, 28 Apr 2024 20:32:10 +0700
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Sending patches as eml message attachment?
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <Zi4bMx2FKuviJi0M@archie.me>
 <2024042828-occupier-confused-e046@gregkh>
 <221f6cfe-07c9-4fc0-a908-84276b8e4088@gmail.com>
 <2024042844-disfigure-dose-e194@gregkh>
Content-Language: en-US
From: Bagas Sanjaya <bagasdotme@gmail.com>
In-Reply-To: <2024042844-disfigure-dose-e194@gregkh>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On 4/28/24 18:18, Greg Kroah-Hartman wrote:
> On Sun, Apr 28, 2024 at 06:10:16PM +0700, Bagas Sanjaya wrote:
>> On 4/28/24 16:56, Greg Kroah-Hartman wrote:
>>> Why would they be?
>>>
>>> Attachments don't usually work as you can not reply to them and comment
>>> on the contents, right?  Try it yourself and see.
>>>
>>
>> OK.
>>
>> I experimented this by sending dummy patches to myself, as attachment.
>> I replied to the patch using mutt and thunderbird. In mutt, the patch
>> contents was quoted, whereas in the latter, it was missing. Hence,
>> email clients are inconsistent on handling patch attachments.
> 
> That is true, which is why we say "do not attach patches".  It's as if
> people assume we are new at this whole thing...
> 

OK, thanks!

-- 
An old man doll... just what I always wanted! - Clara