From: Gerald Pfeifer <gerald@pfeifer.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch, committed] invoke.texi: DWARF, stabs, and ELF
Date: Sun, 18 Mar 2012 21:01:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1203182157190.6944@zbenl.fvgr> (raw)
In-Reply-To: <4F5AB6AF.1070100@codesourcery.com>
On Fri, 9 Mar 2012, Sandra Loosemore wrote:
> Per the DWARF web site
>
> http://dwarfstd.org/Download.php
>
> the correct names of the various versions of the DWARF standard appear
> to be either "DWARF Version N" or "DWARF N", rather than e.g. "DWARF2",
> "DWARF-2", "dwarf2", or whatever. This patch to invoke.texi makes usages
> reflect the official names. Similarly, I've fixed up a couple instances
> of incorrect usage of "stabs" (official name seems to be all lowercase,
> like that) and "ELF".
I like the other changes, but find "DWARF Version N" with an uppercase
V in "Version" a bit unnatural and would prefer to just use the lowercase
"version" here.
Gerald
next prev parent reply other threads:[~2012-03-18 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 2:04 Sandra Loosemore
2012-03-18 21:01 ` Gerald Pfeifer [this message]
2012-03-18 21:28 ` Sandra Loosemore
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=alpine.LNX.2.00.1203182157190.6944@zbenl.fvgr \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--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).