From: Daniel Jacobowitz <drow@false.org>
To: Geoffrey Keating <geoffk@geoffk.org>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Geoffrey Keating <gkeating@apple.com>,
gcc@gcc.gnu.org
Subject: Re: move specs documentation to internals manual?
Date: Sat, 09 Jul 2005 00:23:00 -0000 [thread overview]
Message-ID: <20050709002328.GA3301@nevyn.them.org> (raw)
In-Reply-To: <m21x68khaq.fsf_-_@geoffk.org>
On Fri, Jul 08, 2005 at 04:29:49PM -0700, Geoffrey Keating wrote:
> I agree with both comments here: it's lame that we have duplicated
> documentation (and explains why I didn't realise that I had to change
> two places), and I don't think that we should be considering specs to
> be an user-level interface to GCC.
>
> 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.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-09 0:23 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 [this message]
2005-07-09 0:32 ` Joseph S. Myers
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=20050709002328.GA3301@nevyn.them.org \
--to=drow@false.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
--cc=gkeating@apple.com \
--cc=joseph@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).