From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Sending patches as eml message attachment?
Date: Sun, 28 Apr 2024 13:18:24 +0200 [thread overview]
Message-ID: <2024042844-disfigure-dose-e194@gregkh> (raw)
In-Reply-To: <221f6cfe-07c9-4fc0-a908-84276b8e4088@gmail.com>
On Sun, Apr 28, 2024 at 06:10:16PM +0700, Bagas Sanjaya wrote:
> 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.
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...
greg k-h
next prev parent reply other threads:[~2024-04-28 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 9:47 Sending patches as eml message attachment? Bagas Sanjaya
2024-04-28 9:56 ` Greg Kroah-Hartman
2024-04-28 11:10 ` Bagas Sanjaya
2024-04-28 11:18 ` Greg Kroah-Hartman [this message]
2024-04-28 13:32 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024042844-disfigure-dose-e194@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.