From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: <binutils@sources.redhat.com>, <gdb@sources.redhat.com>,
<gcc@gcc.gnu.org>
Subject: Re: Documenting partial builds (Was Re: ^c now disallowed?)
Date: Sat, 28 Dec 2002 04:11:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0212281209190.9674-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <20021228040534.GA3190@doctormoo>
On Fri, 27 Dec 2002, Nathanael Nerode wrote:
> The big question is, *where* should this be documented? I can document
> the toplevel Makefile interface quite clearly, but I'm very unsure where
> to put said documentation; should I duplicate it in the docs for each
> package (and if so, where in those docs)? Put it in some special
> location? What?
The old toplevel is documented in etc/configure.texi in src, which is
where the GCC internals manual (sourcebuild.texi) currently links to for
documentation of toplevel.
--
Joseph S. Myers
jsm28@cam.ac.uk
prev parent reply other threads:[~2002-12-28 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 20:07 Nathanael Nerode
2002-12-28 4:11 ` Joseph S. Myers [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=Pine.LNX.4.33.0212281209190.9674-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.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