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:09:10 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0707051556000.9434@woody.linux-foundation.org> (raw)
In-Reply-To: <200707050111.43327.dtor@insightbb.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=us-ascii, Size: 1733 bytes --]
[ Ok, pulled. However, it's time for another installment of "Flame that
stupid mail client", because this isn't the first time this bit me ]
On Thu, 5 Jul 2007, Dmitry Torokhov wrote:
>
> Please consider pulling from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
There's somethign wrong with your emails, and it's very irritating.
I cannot just cut-and-paste the whole line, because your tabs and spaces
aren't tabs and spaces, they are some horrible abomination.
What _looks_ like a tab above, when I save it and look at it with "od", it
shows it true nasty life: it's not a tab, and it's not even eight spaces,
it's four copies of the byte sequence '\302\240 ' ('\xC2\xA0\x20'), ie
some horrid nasty three-byte sequence where one character is a space, and
the previous two characters are some utf-8 abomination.
I have no idea what kind of crap you use to generate it, and quite
frankly, I don't want to know. I just want it to stop, so that when I
cut-and-paste, I don't get random UTF-8 characters that just *look* like
spaces but don't act like it, and cause my shell to very reasonably whine
about the result.
I think the "c2 a0" character is the utf-8 representation of a  
(non-breaking space), but:
- you are damn well sending text
- it's followed by a regular space, so it's stupid
- please don't do it.
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.
Sending hidden invisible utf-8 crap that looks like space, but doesn't act
like it, is just damn impolite by kmail. I assume you weren't even aware
of the random crud you are sending out?
Linus
next prev parent reply other threads:[~2007-07-05 23:09 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 [this message]
2007-07-05 23:32 ` Linus Torvalds
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.0707051556000.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®