From: john slee <indigoid@higherplane.net>
To: Larry McVoy <lm@work.bitmover.com>,
Russ Allbery <rra@stanford.edu>,
Felix Domke <tmbinc@elitedvb.net>,
linux-kernel@vger.kernel.org
Subject: Re: Indention - why spaces?
Date: Mon, 30 Dec 2002 14:47:07 +1100 [thread overview]
Message-ID: <20021230034707.GD18508@higherplane.net> (raw)
In-Reply-To: <20021230034303.GA11425@work.bitmover.com>
On Sun, Dec 29, 2002 at 07:43:03PM -0800, Larry McVoy wrote:
> On Sun, Dec 29, 2002 at 07:33:20PM -0800, Russ Allbery wrote:
> > Felix Domke <tmbinc@elitedvb.net> writes:
> >
> > > i don't want to change anything, i just like to know WHY people use
> > > spaces. are they somehow unportable? (i don't think so)
> >
> > <http://www.jwz.org/doc/tabs-vs-spaces.html>
>
> Quouting from that page:
> That ensures that, even if I happened to insert a literal tab in the
> file by hand (or if someone else did when editing this file earlier),
> those tabs get expanded to spaces when I save.
>
> If you are using a source management system, pretty much *any* source
> management system, doing this will cause all the lines to be "rewritten"
> if they had tabs. The fact that this person would advocate changing
> code that they didn't actually change shows a distinct lack of clue.
> No engineer who works for an even semi-pro company would dream of doing
> this. At BitMover, anyone who seriously advocated this for more than
> a day would be fired.
well, he DID work at netscape...
j.
--
toyota power: http://indigoid.net/
next prev parent reply other threads:[~2002-12-30 3:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.f9m4suv.e6ubgf@ifi.uio.no>
2002-12-30 3:33 ` Russ Allbery
2002-12-30 3:43 ` Larry McVoy
2002-12-30 3:47 ` john slee [this message]
2002-12-30 4:26 ` Russ Allbery
2002-12-30 23:20 ` Mark Mielke
2002-12-30 12:28 ` Wichert Akkerman
2002-12-30 12:49 ` John Bradford
2002-12-30 12:57 ` Wichert Akkerman
2002-12-30 13:12 ` Rik van Riel
2002-12-30 13:16 ` Russell King
2002-12-30 13:17 ` Dave Jones
2002-12-30 18:53 ` Emiliano Gabrielli
2002-12-30 19:00 ` Arnaldo Carvalho de Melo
2002-12-30 19:30 ` Herman Oosthuysen
2002-12-30 9:42 ` Zac Hansen
2002-12-30 20:43 ` Felix Domke
2002-12-30 23:26 ` Mark Mielke
2002-12-31 1:02 ` Wichert Akkerman
2002-12-30 23:55 ` Herman Oosthuysen
2002-12-31 2:20 ` Anthony J. Breeds-Taurima
2002-12-31 9:47 ` Christoph Hellwig
[not found] ` <mailman.1041274740.23755.linux-kernel2news@redhat.com>
2002-12-31 5:28 ` Pete Zaitcev
2002-12-31 6:04 ` Larry McVoy
2002-12-30 16:12 ` Larry McVoy
2002-12-31 22:43 Heater, Daniel (IndSys, GEFanuc, VMIC)
-- strict thread matches above, loose matches on Subject: below --
2002-12-31 17:21 Roberto Peon
2002-12-30 2:29 Felix Domke
2002-12-30 11:28 ` Christoph Hellwig
2002-12-31 8:55 ` Tomas Szepe
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=20021230034707.GD18508@higherplane.net \
--to=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=rra@stanford.edu \
--cc=tmbinc@elitedvb.net \
/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
Powered by JetHome