From: Andrew Cagney <ac131313@cygnus.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: Kazu Hirata <kazu@hxi.com>,
binutils@sources.redhat.com, Eli Zaretskii <eliz@is.elta.co.il>
Subject: Re: [patch] *-dis.c: Fix formatting.
Date: Tue, 21 Aug 2001 19:58:00 -0000 [thread overview]
Message-ID: <3B831FC3.3080704@cygnus.com> (raw)
In-Reply-To: <20010819230340.J31523@bubble.sa.bigpond.net.au>
> Your correction to Kazu however, does run foul of the very first rule
> regarding formatting in the GNU coding standard, and we're trying to
> make binutils comply with the standard. bug-standards@gnu.org?
``The good thing about standards is that there are so many to choose
from'' :-)
I've sent an e-mail to bug-standards requesting clarification since I
need to get this resolved for GDB. Indent 1.9.1, which was used to
blindly re-indent GDB two years ago, included -sbi2. The current
indent, 2.2.6, dropped that option. Try re-indenting GDB and the
structs move!
Any way, my gut feeling is that:
struct foo
{
}
is correct (even though it does contradict the opening paragraph).
EMACS source is full of it and indent 2.2.6 switched to it.
enjoy,
Andrew
next prev parent reply other threads:[~2001-08-21 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200108171934.MAA23915@cygnus.com>
2001-08-17 21:34 ` Andrew Cagney
2001-08-17 22:28 ` Alan Modra
2001-08-18 10:08 ` Andrew Cagney
2001-08-18 10:08 ` Andrew Cagney
2001-08-19 6:33 ` Alan Modra
2001-08-21 19:58 ` Andrew Cagney [this message]
2001-08-17 12:33 Kazu Hirata
[not found] <200108121542.IAA18490@cygnus.com>
2001-08-13 1:05 ` Nick Clifton
-- strict thread matches above, loose matches on Subject: below --
2001-08-12 8:42 Kazu Hirata
[not found] <no.id>
2001-07-23 17:10 ` Alan Modra
2001-07-23 7:53 Kazu Hirata
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=3B831FC3.3080704@cygnus.com \
--to=ac131313@cygnus.com \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=eliz@is.elta.co.il \
--cc=kazu@hxi.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).