linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andrew Morton <akpm@osdl.org>,
	axboe@suse.de, alan@lxorguk.ukuu.org.uk, sfr@canb.auug.org.au,
	linux-kernel@vger.kernel.org
Subject: Re: - add-pselect-ppoll-system-call-implementation-tidy.patch	removed from -mm tree
Date: Mon, 23 Jan 2006 18:25:10 +1300	[thread overview]
Message-ID: <1137993911.27828.28.camel@localhost.localdomain> (raw)
In-Reply-To: <43D0B4F5.30807@cosmosbay.com>

On Fri, 2006-01-20 at 11:01 +0100, Eric Dumazet wrote:
> Some readers of linux kernel sources are blind.
> They use a kind of terminal that 'displays' a single line of 80 'characters' 
> (or even 40) called a 'Braille Display'
> 
> This kind of terminal is very expensive, and I think the 80 column one is the 
> most you can get (price : about 7000$).

Yes, I've seen them. What's your point? A user with a braille terminal
can also 'see' that it's just a memcpy of the signal set, and doesn't
really need to scroll over to see the length argument to the memcpy,
except in very exceptional circumstances. The code flow is perfectly
understandable without doing so.

> I am ok to be a litle bit upset by this 80 limitation that looks odd on my 
> 1000$ 24" display, but reminds me the fact that some human people are different.
> 
> So please don't count me as part of your _everyone_.

I count your theoretical blind person above as part of 'everyone'. By
gratuitously moving the 'fluff' onto a new line, he gets a whole line
taken up by it when he scrolls down. If it had stayed where I put it, it
wouldn't be getting in his way.

-- 
dwmw2


  reply	other threads:[~2006-01-23  5:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200601190052.k0J0qmKC009977@shell0.pdx.osdl.net>
2006-01-19  5:21 ` - add-pselect-ppoll-system-call-implementation-tidy.patch removed from -mm tree David Woodhouse
2006-01-19  6:17   ` Stephen Rothwell
2006-01-19  6:24     ` David Woodhouse
2006-01-19  6:30     ` Andrew Morton
2006-01-19  6:40       ` David Woodhouse
2006-01-19  6:36     ` David S. Miller
2006-01-19  6:47       ` Trond Myklebust
2006-01-19  7:02         ` Andrew Morton
2006-01-19  7:18           ` David Woodhouse
2006-01-19  8:09           ` David S. Miller
2006-01-19 15:51       ` James Morris
2006-01-20  2:17       ` Stephen Rothwell
2006-01-19  9:58     ` Alan Cox
2006-01-19 15:59       ` Jens Axboe
2006-01-20  8:33         ` David Woodhouse
2006-01-20  8:44           ` Andrew Morton
2006-01-20  8:59             ` David Woodhouse
2006-01-20 10:01               ` Eric Dumazet
2006-01-23  5:25                 ` David Woodhouse [this message]
2006-01-20 23:44               ` Adrian Bunk

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=1137993911.27828.28.camel@localhost.localdomain \
    --to=dwmw2@infradead.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).