From: Guenter Roeck <linux@roeck-us.net>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Mark Brown <broonie@kernel.org>,
Daniel Santos <daniel.santos@pobox.com>,
Daniel Santos <danielfsantos@att.net>,
linux-gpio <linux-gpio@vger.kernel.org>,
linux-usb <linux-usb@vger.kernel.org>,
linux-spi <linux-spi@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: "Virtual" Interrupts -- Need help please
Date: Mon, 09 Sep 2013 04:45:37 -0700 [thread overview]
Message-ID: <522DB4E1.7080507@roeck-us.net> (raw)
In-Reply-To: <522DAE69.4050608@ahsoftware.de>
On 09/09/2013 04:18 AM, Alexander Holler wrote:
> Am 09.09.2013 13:02, schrieb Mark Brown:
>> On Sun, Sep 08, 2013 at 05:35:56PM -0700, Guenter Roeck wrote:
>>
>> Please fix your mailer to word wrap within paragraphs, not doing this
>> makes your mail very hard to read. It looks like your mailer has also
>> reflowed Daniel's mail.
>
> That's just wrong. Mail readers should wrap lines, not senders. And readers can do this since some decades.
>
> The reason is obvious: No sender knows the line width the receiver can display. So, for example, if the sender hard breaks lines every 80 chars, a reader with a device which just displays 60 characters at max. will see every second line with at most 20 characters. I assume you can guess how such does look like. Furthermore there are still a lot of people which do like to read mails with line length as long their display is possible to show, and hard breaking lines on the receiver side does make such impossible.
>
> So the correct behaviour is to not hard break lines on the sender side and leave that to the reader on the receiving side, as only the receiving side knows the line width.
>
I am using thunderbird and/or mutt. I don't think they reflow anything,
or at least the logged mail doesn't seem to have been reflowed (nor
does the text above).
As for what I write myself, I prefer to wrap manually, meaning automatic
insertion of newlines is turned off. Guess I can not do it right for everyone.
Guenter
next prev parent reply other threads:[~2013-09-09 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 0:19 "Virtual" Interrupts -- Need help please Daniel Santos
2013-09-08 0:52 ` Guenter Roeck
2013-09-08 23:50 ` Daniel Santos
2013-09-09 0:35 ` Guenter Roeck
2013-09-09 11:02 ` Mark Brown
2013-09-09 11:18 ` Alexander Holler
2013-09-09 11:45 ` Guenter Roeck [this message]
2013-09-09 12:00 ` Alexander Holler
2013-09-09 13:45 ` Mark Brown
2013-09-09 14:21 ` Alexander Holler
2013-09-09 11:06 ` Mark Brown
2013-09-09 21:12 ` Daniel Santos
2013-09-10 18:01 ` Mark Brown
2013-09-11 17:59 ` Daniel Santos
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=522DB4E1.7080507@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=daniel.santos@pobox.com \
--cc=danielfsantos@att.net \
--cc=holler@ahsoftware.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=tglx@linutronix.de \
/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