From: David Woodhouse <dwmw2@infradead.org>
To: Jens Axboe <axboe@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: - add-pselect-ppoll-system-call-implementation-tidy.patch removed from -mm tree
Date: Fri, 20 Jan 2006 21:33:15 +1300 [thread overview]
Message-ID: <1137745995.30084.201.camel@localhost.localdomain> (raw)
In-Reply-To: <20060119155933.GX4213@suse.de>
On Thu, 2006-01-19 at 16:59 +0100, Jens Axboe wrote:
> I think the CodingStyle suggestion of 80 chars is just fine. I try to
> stay within that, and I mostly succeed. The occasional over-the-line is
> far better than advocation >> 80 chars per line imho.
I agree. It's that "occasional over-the-line" which Andrew is mucking
about with in the patch which started this thread; the case where it
makes _sense_ to let it go over 80 characters rather than wrapping it.
--
dwmw2
next prev parent reply other threads:[~2006-01-20 8:33 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 [this message]
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
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=1137745995.30084.201.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.