From: Larry McVoy <lm@bitmover.com>
To: Herman Oosthuysen <Herman@WirelessNetworksInc.com>
Cc: linux <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: Re: Indention - why spaces?]
Date: Tue, 31 Dec 2002 08:31:54 -0800 [thread overview]
Message-ID: <20021231163154.GD9423@work.bitmover.com> (raw)
In-Reply-To: <3E11C4E2.2050306@WirelessNetworksInc.com>
> Larry, you can save yourself a lot of trouble, time and money: Create an
> indent configuration file and tell your people to use it. That is
> exactly why indent was written many years ago.
Indent is fine as a first pass, it doesn't handle everything properly.
If it did, I think I would have figured it out by now. And no, I'm
not going to go fix indent, I looked at the problems and the fixes
and decided to pass. Some of them just aren't worth fixing in
indent.
Besides, I really don't believe in giving people crutches, I believe
in teaching them what it is I want and why. That tends to stick.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-12-31 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 16:25 [Fwd: Re: Indention - why spaces?] Herman Oosthuysen
2002-12-31 16:31 ` Larry McVoy [this message]
2002-12-31 17:11 ` Herman Oosthuysen
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=20021231163154.GD9423@work.bitmover.com \
--to=lm@bitmover.com \
--cc=Herman@WirelessNetworksInc.com \
--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