From: Jim Wilson <wilson@tuliptree.org>
To: Sandra Loosemore <sandra@codesourcery.com>,
Gerald Pfeifer <gerald@pfeifer.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] expand -fdebug-prefix-map documentation
Date: Thu, 26 Oct 2017 21:49:00 -0000 [thread overview]
Message-ID: <1509053385.2549.11.camel@tuliptree.org> (raw)
In-Reply-To: <59F22AD5.50703@codesourcery.com>
On Thu, 2017-10-26 at 12:35 -0600, Sandra Loosemore wrote:
> On 10/26/2017 11:47 AM, Gerald Pfeifer wrote:
> > Thanks you for fleshing this out, Jim!
> >
> > This looks fine to me (modula Sandra's note). Just a question:
> > would
> > we refer to GDB instead of gdb here? It feels a little in between
> > to
> > me, whether we are referring to the tool or the actual binary. I'm
> > sure Sandra will have guidance for us. ;-)
> Hmmm, yes. "GDB" is the preferred spelling elsewhere in the manual.
Checked in with the two corrections.
Jim
prev parent reply other threads:[~2017-10-26 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 1:44 Jim Wilson
2017-10-26 17:09 ` Sandra Loosemore
2017-10-26 17:52 ` Gerald Pfeifer
2017-10-26 18:54 ` Sandra Loosemore
2017-10-26 21:49 ` Jim Wilson [this message]
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=1509053385.2549.11.camel@tuliptree.org \
--to=wilson@tuliptree.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=sandra@codesourcery.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).