From: Al Viro <viro@ftp.linux.org.uk>
To: J?rn Engel <joern@wohnheim.fh-wedel.de>
Cc: Ram Pai <linuxram@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>,
mike@waychison.com, bfields@fieldses.org, serue@us.ibm.com
Subject: Re: [RFC PATCH 1/10] vfs: Lindentified namespace.c
Date: Sat, 17 Sep 2005 13:34:57 +0100 [thread overview]
Message-ID: <20050917123457.GJ19626@ftp.linux.org.uk> (raw)
In-Reply-To: <20050917121848.GA9106@wohnheim.fh-wedel.de>
On Sat, Sep 17, 2005 at 02:18:48PM +0200, J?rn Engel wrote:
> On Fri, 16 September 2005 14:39:15 -0700, Ram Pai wrote:
> > On Fri, 2005-09-16 at 14:25, Andrew Morton wrote:
> > > linuxram@us.ibm.com (Ram) wrote:
> > > >
> > > > Lindentified fs/namespace.c
> > >
> > > For something which is as already-close to CodingStyle as namespace.c it's
> > > probably better to tidy it up by hand. Lindent breaks almost as much stuff
> > > as it fixes.
> >
> > I thought Lindent was the gospel for codying style. Looks like its not.
> > Will fix all of them.
>
> It is an approximation. In my personal experience, the "-l80"
> parameter is doing a lot of harm. It causes things like
>
> if (...)
> for (...)
> while (...)
> if (...)
> for (...)
> while (...)
> some_function(argument,
> very_long_argument,
> another_argument,
> 0,
> 1,
> NULL
> );
>
... show up as unreadable crap they are. I fail to see a problem...
Fix them and run Lindent again, that's it.
Lindent behaviour wrt labels is far more annoying, ditto for the mess it
often makes out of prototypes (demonstrated in the patch in question).
IME the best way to use Lindent is to do vi -c 's/[[:space:]]*$//|x' foo.c
first, then run Lindent, then walk through prototypes and fix them,
diff with pre-Lindent version and see if it looks sane...
next prev parent reply other threads:[~2005-09-17 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 18:26 [RFC PATCH 1/10] vfs: Lindentified namespace.c Ram
2005-09-16 18:51 ` Alexey Dobriyan
2005-09-16 20:55 ` Benjamin LaHaise
2005-09-16 21:29 ` Ram Pai
2005-09-16 21:25 ` Andrew Morton
2005-09-16 21:38 ` Matthew Wilcox
2005-09-16 21:39 ` Ram Pai
2005-09-17 12:18 ` Jörn Engel
2005-09-17 12:34 ` Al Viro [this message]
2005-09-17 13:33 ` Jörn Engel
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=20050917123457.GJ19626@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@osdl.org \
--cc=bfields@fieldses.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mike@waychison.com \
--cc=miklos@szeredi.hu \
--cc=serue@us.ibm.com \
/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