From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Geoffrey Keating <geoffk@geoffk.org>,
Geoffrey Keating <gkeating@apple.com>,
gcc@gcc.gnu.org
Subject: Re: move specs documentation to internals manual?
Date: Sat, 09 Jul 2005 00:32:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0507090029520.18765@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20050709002328.GA3301@nevyn.them.org>
On Fri, 8 Jul 2005, Daniel Jacobowitz wrote:
> > So, what do people think about (a) deleting the big comment in gcc.c
> > that tries to explain specs (leaving a pointer to the manual), and (b)
> > moving the specs documentation to the internals manual?
>
> I think it's a good idea - but someone should compare the two existing
> bits of documentation first, since IIRC I've seen people add to one but
> not the other.
Agreed. The documentation of -dumpspecs and -specs= should point to the
internals manual information on specs, but that should be the only
reference needed in the user manual.
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)
next prev parent reply other threads:[~2005-07-09 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050708054604.67D4A15D66FE@geoffk5.apple.com>
[not found] ` <m3vf3lvld8.fsf@gossamer.airs.com>
[not found] ` <Pine.LNX.4.61.0507081217260.14395@digraph.polyomino.org.uk>
2005-07-08 23:29 ` Geoffrey Keating
2005-07-09 0:23 ` Daniel Jacobowitz
2005-07-09 0:32 ` Joseph S. Myers [this message]
2005-07-09 0:32 ` Joel Sherrill <joel@OARcorp.com>
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=Pine.LNX.4.61.0507090029520.18765@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
--cc=gkeating@apple.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).