From: "David S. Miller" <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: dwmw2@infradead.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: - add-pselect-ppoll-system-call-implementation-tidy.patch removed from -mm tree
Date: Wed, 18 Jan 2006 22:36:29 -0800 (PST) [thread overview]
Message-ID: <20060118.223629.100108404.davem@davemloft.net> (raw)
In-Reply-To: <20060119171708.7f856b42.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 19 Jan 2006 17:17:08 +1100
> 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.
I wish there were an exception for function prototypes and definitions.
Why? So grep actually works.
Hmmm, what args does function X take? Let's try this:
bash$ git grep X
Oops, the args went past 80 columns and was split up, so I only
get the first few in the grep output.
next prev parent reply other threads:[~2006-01-19 6:36 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 ` 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 [this message]
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
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=20060118.223629.100108404.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--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
Powered by JetHome