From: "Drew DeVault" <sir@cmpwn.com>
To: "Greg KH" <gregkh@linuxfoundation.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>
Cc: "Eric Wong" <e@80x24.org>, <workflows@vger.kernel.org>
Subject: Re: patch attachments still unwelcome?
Date: Mon, 04 Nov 2019 08:42:59 -0500 [thread overview]
Message-ID: <BY75NACT4RE6.3FMUPXJYHLVZK@homura> (raw)
In-Reply-To: <20191104134206.GA2133491@kroah.com>
Also pitching in with a vote against patches-as-attachments. My mailing
list software doesn't know how to deal with these and I don't really
want to teach it about them.
next prev parent reply other threads:[~2019-11-04 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 2:27 patch attachments still unwelcome? Eric Wong
2019-11-01 9:04 ` Greg KH
2019-11-04 13:13 ` Theodore Y. Ts'o
2019-11-04 13:23 ` Dmitry Vyukov
2019-11-04 14:49 ` Jani Nikula
2019-11-04 17:40 ` Geert Uytterhoeven
2019-11-05 10:46 ` Geert Uytterhoeven
2019-11-04 13:42 ` Greg KH
2019-11-04 13:42 ` Drew DeVault [this message]
2019-11-01 13:00 ` Konstantin Ryabitsev
2019-11-04 11:26 ` Mark Brown
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=BY75NACT4RE6.3FMUPXJYHLVZK@homura \
--to=sir@cmpwn.com \
--cc=e@80x24.org \
--cc=gregkh@linuxfoundation.org \
--cc=tytso@mit.edu \
--cc=workflows@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).