From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Bernd Schmidt <bernds@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>, <gcc@gcc.gnu.org>
Subject: Re: A bit of vector extension documentation
Date: Thu, 27 Sep 2001 08:32:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.33.0109271731070.737-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <Pine.LNX.4.33.0109271556440.27756-100000@host140.cambridge.redhat.com>
On Thu, 27 Sep 2001, Bernd Schmidt wrote:
> I'm not sure about this - do we want to treat the manual as a unit, or do
> we want to keep the user and developer parts separated as far as possible?
Probably separate (at least this was Jeff's plan), but we can refer from
one manual to the other; I forget how exactly this is acomplished, but we
do that somewhere in the installation instructions and I could try to dig
it out if you want.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2001-09-27 8:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.33.0109271622590.737-100000@naos.dbai.tuwien.ac.at>
2001-09-27 8:06 ` Bernd Schmidt
2001-09-27 8:24 ` Jan Hubicka
2001-09-27 8:45 ` Bernd Schmidt
2001-09-27 8:32 ` Gerald Pfeifer [this message]
2001-09-27 9:04 ` Matt Kraai
2001-09-27 11:34 ` Daniel Jacobowitz
2001-09-27 12:33 ` Richard Henderson
2001-09-27 12:37 ` Bernd Schmidt
2001-09-27 12:44 ` Richard Henderson
2001-09-27 12:45 ` Bernd Schmidt
2001-09-28 0:05 ` Daniel Egger
2001-09-28 0:39 ` Richard Henderson
2001-09-28 0:59 ` Daniel Egger
2001-09-28 1:32 ` Richard Henderson
2001-09-28 1:56 ` Daniel Egger
2001-09-28 8:48 ` Daniel Berlin
2001-09-28 9:38 ` Richard Henderson
2001-09-28 10:13 ` David Edelsohn
2001-09-28 10:25 ` Diego Novillo
2001-09-28 12:11 ` Toon Moene
2001-09-28 12:45 ` Diego Novillo
2001-09-28 13:21 ` Tim Prince
2001-09-29 14:33 ` Aldy Hernandez
2001-09-28 15:37 ` Daniel Berlin
2001-09-29 17:11 ` Daniel Berlin
2001-09-29 19:37 ` Richard Henderson
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.BSF.4.33.0109271731070.737-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=bernds@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/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).