From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Joel Brobecker <brobecker@adacore.com>,
Mike Frysinger <vapier@gentoo.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Doug Evans <dje@google.com>
Subject: Re: Fix spelling error in psim
Date: Thu, 21 Aug 2014 13:46:00 -0000 [thread overview]
Message-ID: <53F5F848.9040709@oarcorp.com> (raw)
In-Reply-To: <20140821071535.GK1773@adacore.com>
On 8/21/2014 2:15 AM, Joel Brobecker wrote:
>>> [If this were gdb one might want a "." followed by two spaces here,
>>> but this isn't gdb. Lucky you. :-)]
>> that's enforced in new code (which psim is anything but). i'd have no
>> problem if someone felt like going through and cleaning that
>> particular issue up in the whole code base.
>>
>> sim should be following GNU style conventions. i dislike them, but
>> it's part of a larger GNU project, so deviating anyways would be bad
>> form :).
> Interestingly, I have always considered sim to be part of the GDB
> project, and therefore under GDB coding style.
>
Let me fix the spelling issues first. Is that OK?
I am not opposed to fixing the style issues but really don't have to get
sucked into them right now.
Can uncrustify or some other tool help?
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2014-08-21 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 22:45 Joel Sherrill
2014-08-21 0:10 ` Doug Evans
2014-08-21 1:14 ` Mike Frysinger
2014-08-21 7:15 ` Joel Brobecker
2014-08-21 8:12 ` Mike Frysinger
2014-08-21 13:46 ` Joel Sherrill [this message]
2014-08-27 6:08 ` Joel Brobecker
2014-08-21 1:13 ` Mike Frysinger
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=53F5F848.9040709@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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