mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: David Newall <davidn@davidnewall.com>
Cc: "Jayson R. King" <dev@jaysonking.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH 0/4] BFS backport to 2.6.27
Date: Mon, 05 Oct 2009 16:20:29 -0400	[thread overview]
Message-ID: <168327.1254774029@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 06 Oct 2009 03:34:48 +1030." <4ACA2730.7000006@davidnewall.com>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

On Tue, 06 Oct 2009 03:34:48 +1030, David Newall said:

> Yes, I was trying for irony.  Mime has been around for many decades and
> anybody claiming that they can't cope with them is probably very stupid
> or lying to make some strange point.  Anyway, I'm not trying to change
> the policy, but was only have a snide dig, en passant, at the crufty,
> old, has-been attitude that it represents.

The problem is that with most MUAs, if you do a 'reply and quote text',
it only operates correctly on the first/main body part - doing a 'reply and
quote' to an *attachment* is usually a lot harder, and doing a 'reply and
quote text from both main body and attachment' is usually convoluted enough
that 'Just Hit Delete' becomes tempting...

I've submitted my share of one-liner patches, and they've all been
PGP-signed, so they show up as MIME multiparts - and yet I've never ONCE
been asked to change it.  I have to conclude that it's because although it's
a multipart, it's a multipart that DTRT when a maintainer hits 'reply' -
and that production MUAs still DTWT when dealing with replying to the
attachments rather than the main body....

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2009-10-05 20:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05  9:16 Jayson R. King
2009-10-05  9:45 ` [PATCH 1/4] fix scaled & unscaled cputime accounting Jayson R. King
2009-10-05  9:45 ` [PATCH 2/4] idle " Jayson R. King
2009-10-05  9:46 ` [PATCH 3/4] sched: account system time properly Jayson R. King
2009-10-05  9:46 ` [PATCH 4/4] BFS backport to 2.6.27 Jayson R. King
2009-10-05 10:02 ` [PATCH 0/4] " Jayson R. King
2009-10-05 10:26 ` Jayson R. King
2009-10-05 14:12   ` David Newall
2009-10-05 16:02     ` Jayson R. King
2009-10-05 17:04       ` David Newall
2009-10-05 20:20         ` Valdis.Kletnieks [this message]

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=168327.1254774029@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=davidn@davidnewall.com \
    --cc=dev@jaysonking.com \
    --cc=kernel@kolivas.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®