workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: workflows@vger.kernel.org
Subject: patch attachments still unwelcome?
Date: Fri, 1 Nov 2019 02:27:46 +0000	[thread overview]
Message-ID: <20191101022746.GA25491@dcvr> (raw)

The BDFL sets an example by attaching patches:

https://lore.kernel.org/lkml/?q=f%3Atorvalds+n%3Apatch

So the documentation in the kernel advising against sending
patch attachments seems hypocritical.  Changing the kernel docs
allow patch attachments could be a good start to making life
easier for contributors without SMTP or IMAP access.

Are many MUAs still incapable of handling them?
mutt shows text patches inline, at least.

I've already been making public-inbox look harder for pre/post-image
OIDs in attachments that it wouldn't decode before:

https://public-inbox.org/meta/20191031031220.21048-1-e@80x24.org/

And I'm considering making it handle application/octet-stream, too;
since patches do end up with the wrong Content-Type, sometimes:

https://lore.kernel.org/lkml/CANAwSgRs2DUXwvhJD5qpXg04qEdP_Nt-wQqRbD2FpY2SWnHpAA@mail.gmail.com/

             reply	other threads:[~2019-11-01  2:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01  2:27 Eric Wong [this message]
2019-11-01  9:04 ` patch attachments still unwelcome? 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
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=20191101022746.GA25491@dcvr \
    --to=e@80x24.org \
    --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).