From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Benjamin LaHaise <bcrl@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] reformat mtrr.c to conform to CodingStyle
Date: Tue, 13 Nov 2001 14:11:54 -0500 [thread overview]
Message-ID: <3BF1707A.B8AA4F2D@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>
Chris Wedgwood wrote:
>
> On Tue, Nov 13, 2001 at 09:04:33AM -0800, Linus Torvalds wrote:
>
> I don't like reformatting without at least asking the maintainer,
> unless the maintainer isn't doing maintenance. Also, right now I'd
> rather not have any big patches even if they are just
> syntactic.. Makes hand-over to Marcelo simpler.
>
> 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....
True. For mtrr.c it (a) is unmaintained for years, and (b) is actively
being hacked on by non-maintainers.
It has an especially strong case for Lindent'ing.
Jeff
--
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-13 19:12 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 [this message]
2001-11-14 10:42 ` Helge Hafting
2001-11-14 15:30 ` Jeff Garzik
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=3BF1707A.B8AA4F2D@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=bcrl@redhat.com \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.