Re: - add-pselect-ppoll-system-call-implementation-tidy.patch removed from -mm tree

[Andrew Morton <akpm@osdl.org>]

Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Documentation/CodingStyle says:
> 
>  The limit on the length of lines is 80 columns and this is a hard limit.
> 
>  Statements longer than 80 columns will be broken into sensible chunks.
>  Descendants are always substantially shorter than the parent and are placed
>  substantially to the right. The same applies to function headers with a long
>  argument list. Long strings are as well broken into shorter strings.

That's pretty stern.

I'd be happy with a 96-col standard, or 100 or whatever - it's more
convenient and I use twin 20" guns.  But other people have different
hardware constraints and different work practices, so they want 80 cols. 
If we're going to get down and change the standard then OK, let's have that
bunfight.  But while there's a standard we should stick to it so we don't
screw over the people who like to use standard-sized xterms.

And yes, some editors can do sideways-scrolling to make wider-than-80
acceptable in an 80-col window.  But other people's setups don't do that,
and the cost to those people of wrappy code is higher than the cost of
looking at standardly-laid-out code to fancy-editor users.

So the lowest common denominator wins, because they hurt more than anyone
else if we go outside 80-cols.  I use 80-col xterms precisely for this
reason: so that the code which goes in will look OK to those users.