From: Andreas Dilger <adilger@turbolabs.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
Ion Badulescu <ion@cs.columbia.edu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [CFT] [JANITORIAL] Unbork fs.h
Date: Fri, 4 Jan 2002 01:59:10 -0700 [thread overview]
Message-ID: <20020104015910.L12868@lynx.no> (raw)
In-Reply-To: <200201031605.g03G57e22947@guppy.limebrokerage.com> <20020103150705.F25846@conectiva.com.br> <20020103123623.X12868@lynx.no> <E16MOQT-0001Az-00@starship.berlin>
In-Reply-To: <E16MOQT-0001Az-00@starship.berlin>; from phillips@bonn-fries.net on Fri, Jan 04, 2002 at 08:05:56AM +0100
OK, for people that care, I did a quick survey of the changes I made. My
idea is to conform to what is the current "standard" coding style, and not
necessarily what was thrown into Lindent, so that running Lindent on sources
will change as little as is necessary to make it "standard".
I also checked the l-k archives a bit to confirm the changes match the
formatting of the examples given by the King Penguin.
Sadly, lksr is not responding, so I can't look at the history of changes
to Lindent. Is there another kernel CVS with CVSWeb that was as complete
as lksr?
On Jan 04, 2002 08:05 +0100, Daniel Phillips wrote:
> On January 3, 2002 08:36 pm, Andreas Dilger wrote:
> > I removed the following two options:
> > -bs: Put a space between sizeof and its argument.
grep -r "sizeof (" linux | wc -l,
grep -r "sizeof(" linux | wc -l:
sizeof (foo): 1611, sizeof(foo): 19364 => -bs should be removed
> > -psl: Put the type of a procedure on the line before its name.
grep -r -B2 "^{" linux | grep "^[^ ]*(" | wc -l,
grep -r -B2 "^{" linux | grep "^.* .*(" | wc -l:
int
foo(int x): 11408, int foo(int x): 57275 => -psl should be removed
> > I added the following options:
> > -nbbo: don't prefer to break lines before boolean operators
grep -r "[&|][&|][ ^I]*$" | wc -l,
grep -r "^[ ^I]*[&|][&|]" | wc -l:
&& foo): 3338,
(foo &&: 12003 => -nbbo should be added
> > -ci8: indent continuation lines 8 characters
Hard to measure.
> > -ncs: Do not put a space after cast operators.
grep -r "\*) [a-z_(]" . | wc -l,
grep -r "\*)[a-z_(]" . | wc -l:
(void *) foo: 11274, (void *)foo: 17062 => -ncs should be added
> Not putting a space after a cast is gross ;)
Well, it seems you are in the (slight) minority on this one. It's not as
big a margin as the other ones, but still measurable. I wasn't able to
find any examples from the King Penguin himself on this one. Maybe that
means casts are evil and we should strive to rid the world of them? ;-)
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-04 9:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 12:47 [CFT] [JANITORIAL] Unbork fs.h Daniel Phillips
2002-01-03 14:03 ` Daniel Phillips
2002-01-03 15:45 ` Christoph Hellwig
2002-01-03 16:20 ` Daniel Phillips
2002-01-03 16:47 ` Alexander Viro
2002-01-03 17:25 ` Daniel Phillips
2002-01-03 18:25 ` Daniel Phillips
2002-01-03 18:35 ` Christoph Hellwig
2002-01-03 16:45 ` Alexander Viro
2002-01-03 18:04 ` Daniel Phillips
2002-01-03 16:05 ` Ion Badulescu
2002-01-03 16:34 ` Daniel Phillips
2002-01-03 16:28 ` Martin Dalecki
2002-01-03 16:45 ` Arnaldo Carvalho de Melo
2002-01-03 16:36 ` Arnaldo Carvalho de Melo
2002-01-03 17:05 ` Daniel Phillips
2002-01-03 17:07 ` Arnaldo Carvalho de Melo
2002-01-03 19:36 ` Andreas Dilger
2002-01-04 7:05 ` Daniel Phillips
2002-01-04 8:59 ` Andreas Dilger [this message]
2002-01-04 10:02 ` Jeff Garzik
2002-01-03 23:25 ` J.A. Magallon
2002-01-04 1:44 ` Daniel Phillips
2002-01-04 14:52 ` J.A. Magallon
2002-01-03 18:53 ` Daniel Phillips
2002-01-03 20:31 ` Ion Badulescu
-- strict thread matches above, loose matches on Subject: below --
2002-01-04 15:16 Andries.Brouwer
2002-01-04 22:20 ` Andreas Dilger
2002-01-04 23:33 ` Daniel Phillips
2002-01-04 16:45 Bryan Henderson
2002-01-04 22:15 ` Andreas Dilger
2002-01-05 1:07 Bryan Henderson
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=20020104015910.L12868@lynx.no \
--to=adilger@turbolabs.com \
--cc=acme@conectiva.com.br \
--cc=ion@cs.columbia.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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