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] [thread-next>] [day] [month] [year] [list]

Message-ID: <221f6cfe-07c9-4fc0-a908-84276b8e4088@gmail.com>
Date: Sun, 28 Apr 2024 18:10:16 +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 16:56, Greg Kroah-Hartman wrote:
> On Sun, Apr 28, 2024 at 04:47:31PM +0700, Bagas Sanjaya wrote:
>> Hi Greg,
>>
>> Sometimes I'm tempted to send patches as .eml attachments (just like in
>> error messages sent by mail servers to me). Is patch submission by
>> aforementioned way accepted?
> 
> No.
> 
>> If not, why?
> 
> 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.

> Also, .eml is an odd standard, what's wrong with text?
> 

It's also text format like mbox or git-format-patch(1) patches,
though.

Thanks.

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