From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] TI msp430 architecture support
Date: Tue, 25 Jun 2013 15:55:00 -0000 [thread overview]
Message-ID: <20130625085137.4317c9b8@pinnacle.lan> (raw)
In-Reply-To: <87txkmtghb.fsf@fleche.redhat.com>
On Tue, 25 Jun 2013 08:25:20 -0600
Tom Tromey <tromey@redhat.com> wrote:
> >>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
>
> Kevin> I fixed the formatting issues that you noticed and then, for
> Kevin> good measure, I ran the file through gdb_indent.sh. I should've
> Kevin> run gdb_indent.sh over msp430-tdep.c prior to submitting it.
>
> I didn't know anybody used gdb_indent.sh. Was this a one-off thing or
> have you run it regularly on other source files?
There was a time when the output of GNU indent was considered the
standard for GDB indentation. If there was any disagreement about
correct indentation, a contributor would be asked to run GNU indent
over the code. The problem is, of course, that different options
produce different results which is how gdb_indent.sh came into being.
My recollection is that there were at least two occasions when
significant portions of the gdb source tree were reindented. (This
may have pre-dated the creation of gdb_indent.sh, however.) I don't
think that mass reindentation should be done very often because it
causes a lot more work for folks who have developed significant
changes prior to the the reindenation occurring. I think it can make
sense for newly contributed files, however.
Kevin
next prev parent reply other threads:[~2013-06-25 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 3:00 Kevin Buettner
2013-05-17 6:29 ` Joel Brobecker
2013-06-25 1:59 ` Kevin Buettner
2013-06-25 14:40 ` Tom Tromey
2013-06-25 15:55 ` Kevin Buettner [this message]
2013-08-02 20:14 ` Stan Shebs
2013-05-17 11:16 ` Pedro Alves
2013-05-17 17:44 ` Mike Frysinger
2013-05-17 17:55 ` Mike Frysinger
2013-05-17 18:05 ` Tom Tromey
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=20130625085137.4317c9b8@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.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