From: Phil Edwards <phil@jaj.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: toplevel doc, first draft
Date: Mon, 30 Dec 2002 07:06:00 -0000 [thread overview]
Message-ID: <20021230100545.A31236@disaster.jaj.com> (raw)
In-Reply-To: <20021230115943.GA833@doctormoo>; from neroden@twcny.rr.com on Mon, Dec 30, 2002 at 06:59:43AM -0500
On Mon, Dec 30, 2002 at 06:59:43AM -0500, Nathanael Nerode wrote:
> And information on where to put the
> documentation when it's ready is always welcome; etc/configure.texi is soooo
> out-of-date I don't know what to make of it.
We still have an etc directory? I thought it was killed a while ago.
> The Makefile for a subdirectory is expected to provide the usual public
> targets: all, install, info, etc.
I think there's an official recommended list somewhere in the pesky GNU
Coding Standards[tm].
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next prev parent reply other threads:[~2002-12-30 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 4:01 Nathanael Nerode
2002-12-30 7:06 ` Phil Edwards [this message]
2002-12-30 10:25 ` Joseph S. Myers
2002-12-30 7:56 Michael Elizabeth Chastain
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=20021230100545.A31236@disaster.jaj.com \
--to=phil@jaj.com \
--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