From: viro@parcelfarce.linux.theplanet.co.uk
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Davide Libenzi" <davidel@xmailserver.org>,
"Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5 Documentation/CodingStyle ANSI C function declarations.
Date: Fri, 30 May 2003 23:55:04 +0100 [thread overview]
Message-ID: <20030530225504.GK9502@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0305301546580.3089-100000@home.transmeta.com>
On Fri, May 30, 2003 at 03:49:12PM -0700, Linus Torvalds wrote:
>
> On Fri, 30 May 2003, Davide Libenzi wrote:
> >
> > Talking about the code, there are still a bunch of files that uses spaces
> > with tabsize=4. Shouldn't those be reformatted with real TABs ? An emacs
> > lisp (indent+tabify) might do it pretty fast ...
>
> I don't generally like changing syntactic stuff without a reason.
>
> A good reason is when the original maintainer is not that active any more,
> and a new maintainer (or even just random fixer) feels that they need to
> run indent on the sources in order to make them more readable before
> doign a fix.
>
> It happens, but not very often. Alan and Al both do it to the files they
> clean up. But I don't like having it done "just because" - there should be
> a real underlying reason.
FWIW, I'd ran Lindent maybe 10 times or so - only in truly appalling cases
when it hurts just looking at the code (drivers/block/paride, mostly - just
take a look at it in 2.4). Usually it's more of "I change that function;
might as well reindent it" and it's done manually.
next prev parent reply other threads:[~2003-05-30 22:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 19:57 [PATCH] 2.5 Documentation/CodingStyle ANSI C function declarations Steven Cole
2003-05-30 20:14 ` Jörn Engel
2003-05-30 20:25 ` Steven Cole
2003-05-30 20:40 ` Jörn Engel
2003-05-30 20:48 ` Linus Torvalds
2003-05-30 21:20 ` Jörn Engel
2003-05-30 21:38 ` Linus Torvalds
2003-05-30 22:26 ` Jörn Engel
2003-05-30 22:39 ` Davide Libenzi
2003-05-30 22:23 ` Alan Cox
2003-05-30 23:29 ` Davide Libenzi
2003-05-30 22:49 ` Linus Torvalds
2003-05-30 22:55 ` viro [this message]
2003-05-30 22:58 ` Jörn Engel
2003-05-30 23:08 ` Riley Williams
2003-05-30 21:06 ` Jörn Engel
2003-05-30 21:09 ` Russell King
2003-05-30 21:17 ` Linus Torvalds
2003-05-31 0:55 ` Steven Cole
2003-05-31 3:12 ` Arnaldo Carvalho de Melo
2003-05-31 5:08 ` Steven Cole
2003-05-31 5:24 ` Michael Frank
2003-05-31 6:27 ` Bernd Eckenfels
2003-05-31 7:17 ` Bernd Eckenfels
2003-06-02 10:53 ` Juan Quintela
2003-06-02 15:59 ` Linus Torvalds
2003-06-02 16:39 ` Steven Cole
2003-06-02 17:34 ` Arnaldo Carvalho de Melo
2003-06-02 17:55 ` Steven Cole
2003-06-02 17:56 ` Jörn Engel
2003-06-02 16:40 ` Arnaldo Carvalho de Melo
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=20030530225504.GK9502@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=davidel@xmailserver.org \
--cc=joern@wohnheim.fh-wedel.de \
--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.