From: Joel Brobecker <brobecker@gnat.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: usage of tab in the indentation...
Date: Thu, 12 Sep 2002 12:45:00 -0000 [thread overview]
Message-ID: <20020912194531.GC1105@gnat.com> (raw)
In-Reply-To: <3D80E9D5.5AACB552@redhat.com>
> For my part, I just use emacs' default formatting, which
> pretty much relieves me of worrying about formatting, since
> it almost always conforms to the coding standard. And emacs
> uses tabs. It would be a nuisance for me to have to change.
That's fair enough. I know it would cause some of us some problems
to switch to spaces, so wasn't really hoping for a change in policy,
but I'm still curious as to why we used tabs and not spaces. What are
the benefits?
In the meantime, I take it people will not yell if the indentation in a
patch looks a bit bizarre :-)...
--
Joel
next prev parent reply other threads:[~2002-09-12 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 12:06 Joel Brobecker
2002-09-12 12:24 ` Michael Snyder
2002-09-12 12:45 ` Joel Brobecker [this message]
2002-09-12 14:13 ` Kevin Buettner
2002-09-12 17:58 ` Michael Snyder
2002-09-12 18:26 ` Tom Tromey
2002-09-12 18:40 ` Andrew Cagney
2002-09-19 4:34 ` Eli Zaretskii
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=20020912194531.GC1105@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox