From: Michael Elizabeth Chastain <mec@shout.net>
To: neroden@twcny.rr.com, phil@jaj.com
Cc: binutils@sources.redhat.com, gcc@gcc.gnu.org, gdb@sources.redhat.com
Subject: Re: toplevel doc, first draft
Date: Mon, 30 Dec 2002 10:04:00 -0000 [thread overview]
Message-ID: <200212301556.gBUFu1q03502@duracef.shout.net> (raw)
There is a list of standard targets in "info make", node
"standard targets for users".
I think it would be fine to say: "the standard targets (all, install,
info, et cetera)" as documented in 'info make', node 'standard targets
for users'". People are very inductive and love examples, and then
you can point to an authoritative list.
I read all the notes. They struck me as great notes that need preservation,
but they could use more narrative to tie them all together. But as long
as they are accurate then any docs are fine with me. My two cents.
Michael C
next reply other threads:[~2002-12-30 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 10:04 Michael Elizabeth Chastain [this message]
2002-12-31 8:48 ` Ranjit Mathew
-- strict thread matches above, loose matches on Subject: below --
2002-12-30 7:35 Nathanael Nerode
2002-12-30 8:29 ` Phil Edwards
2002-12-30 12:42 ` Joseph S. Myers
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=200212301556.gBUFu1q03502@duracef.shout.net \
--to=mec@shout.net \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--cc=phil@jaj.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).