linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Mark Brown <broonie@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	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 13:18:01 +0200	[thread overview]
Message-ID: <522DAE69.4050608@ahsoftware.de> (raw)
In-Reply-To: <20130909110257.GU29403@sirena.org.uk>

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.

Alexander Holler


  reply	other threads:[~2013-09-09 11:19 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 [this message]
2013-09-09 11:45           ` Guenter Roeck
2013-09-09 12:00             ` Alexander Holler
2013-09-09 13:45           ` Mark Brown
     [not found]             ` <20130909134558.GY29403-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
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=522DAE69.4050608@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=broonie@kernel.org \
    --cc=daniel.santos@pobox.com \
    --cc=danielfsantos@att.net \
    --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=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).