From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Helge Hafting <helgehaf@idb.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reformat mtrr.c to conform to CodingStyle
Date: Wed, 14 Nov 2001 10:30:20 -0500 [thread overview]
Message-ID: <3BF28E0C.C32ACD63@mandrakesoft.com> (raw)
In-Reply-To: <20011112232539.A14409@redhat.com> <Pine.LNX.4.33.0111130903350.16316-100000@penguin.transmeta.com> <20011114080505.A18098@weta.f00f.org> <3BF24AB2.1C8232C0@idb.hist.no>
Helge Hafting wrote:
>
> Chris Wedgwood wrote:
>
> > If (at some point) people do want coding-style patches then there are
> > MANY places (eg. entire filesystem sub-trees) which could have
> > white-space alignment changes and similar things....
>
> Creating lots of such patches looks like unnecessary work to me.
> Why not let Linus run Lindent on the whole tree and be done with it?
> find linux/ -name "*.[ch]" | linux/scripts/Lindent
Lindent still does a few dumb things which make me review the code after
formatting and before submission...
Also, Christoph Hellewig ported NetBSD's indent, which is supposedly a
bit better overall than GNU indent. Something else to look into.
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-14 15:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 4:25 [PATCH] reformat mtrr.c to conform to CodingStyle Benjamin LaHaise
2001-11-13 17:04 ` Linus Torvalds
2001-11-13 19:05 ` Chris Wedgwood
2001-11-13 19:11 ` Jeff Garzik
2001-11-14 10:42 ` Helge Hafting
2001-11-14 15:30 ` Jeff Garzik [this message]
2001-11-14 16:56 ` Christoph Hellwig
2001-11-13 19:10 ` Andreas Dilger
2001-11-13 19:18 ` Benjamin LaHaise
2001-11-13 19:21 ` Momchil Velikov
2001-11-13 19:21 ` Jeff Garzik
2001-11-14 7:57 ` David Weinehall
2001-11-14 8:04 ` David S. Miller
2001-11-14 8:15 ` Jeff Garzik
2001-11-20 8:47 ` Mark van Walraven
2001-11-20 9:52 ` David Weinehall
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=3BF28E0C.C32ACD63@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=helgehaf@idb.hist.no \
--cc=linux-kernel@vger.kernel.org \
/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