From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull][resend] Input updates for 2.6.22-rc7
Date: Thu, 5 Jul 2007 16:32:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0707051618040.9434@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0707051556000.9434@woody.linux-foundation.org>
On Thu, 5 Jul 2007, Linus Torvalds wrote:
>
> It says your user-agent is "Kmail", and maybe there is some way to fix it.
> And if kmail is correct, please make a bug-report to the kmail people.
Ok, googling for kmail, I think it really is kmail doing it, because I
find others complaining about the same idiocy.
Btw, the others who noticed this weren't _nearly_ as polite as I am about
kmail.
Apparently kmail - at least when cutting-and-pasting - will actually turn
every other space into an NBSP for some internal idiotic reason. So even
if you _originally_ had 8 spaces, Kmail will apparently corrupt your data
when cutting-and-pasting according to that other report I saw.
Please stop using kmail, or ask for it to get fixed.
I'm constantly surprised by just how _many_ ways MUA's find to screw up.
It's not like they seem to all have some stupid bug. It's more like they
seem to all have willfully added code explicitly to mess up the content of
email, often with the goal of making it "look" right, even if it's crap.
In this case, it means that you cannot cut-and-paste simple ASCII text,
because Kmail messed up.
Linus
next prev parent reply other threads:[~2007-07-05 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 5:11 Dmitry Torokhov
2007-07-05 23:09 ` Linus Torvalds
2007-07-05 23:32 ` Linus Torvalds [this message]
2007-07-05 23:50 ` Jesper Juhl
2007-07-06 1:01 ` Linus Torvalds
2007-07-06 3:40 ` Dmitry Torokhov
2007-07-06 4:06 ` Linus Torvalds
2007-07-06 21:21 ` plain text MUAs (Re: [git pull][resend] Input updates for 2.6.22-rc7) Oleg Verych
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=alpine.LFD.0.98.0707051618040.9434@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dtor@insightbb.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 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®