From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Roland Schwingel <roland.schwingel@onevision.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Add dll trampoline code handling for windows 64bit
Date: Thu, 15 Mar 2012 14:27:00 -0000 [thread overview]
Message-ID: <87fwdac53f.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120314210310.GJ2853@adacore.com> (Joel Brobecker's message of "Wed, 14 Mar 2012 14:03:10 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> That is very odd, the script should indeed indent the sources
Joel> in a way that follows the GNU Coding Standards. Perhaps we are
Joel> missing some parameters in the call to that script that override
Joel> certain defaults that may no longer match our standards.
When I looked at this for GCC, some years ago now, GNU indent did not
have all the needed options to really mimic GNU style as actually used.
I would like it if we could use some indentation tool.
This would remove a lot of drudgery from patch review.
But, this would require someone doing an investigation into the existing
tools to see if they can do the job. Maybe GNU indent is better now
(though I never heard a response to my various bug reports); or maybe
uncrustify (http://uncrustify.sourceforge.net/) is good enough.
Right now, unless someone volunteers to do the above, I think we should
remove gdb_indent.sh as being actively confusing.
Here's a starting point for uncrustify:
http://debbugs.gnu.org/db/63/6318.html
This bug has a GNU-ish config file attached.
Tom
next prev parent reply other threads:[~2012-03-15 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 20:38 Roland Schwingel
2012-03-14 21:03 ` Joel Brobecker
2012-03-14 23:54 ` Stan Shebs
2012-03-15 14:27 ` Tom Tromey [this message]
2012-03-15 15:26 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2012-03-14 13:36 Roland Schwingel
2012-03-14 15:34 ` Tom Tromey
2012-03-14 16:13 ` Joel Brobecker
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=87fwdac53f.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=roland.schwingel@onevision.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