linux-kernel - Re: Sending patches as eml message attachment?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ee12e2f4-3e43-406b-816a-5f5822002f39@gmail.com>
Date: Sun, 28 Apr 2024 20:32:10 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Sending patches as eml message attachment?

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