From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Mark Mitchell <mark@codesourcery.com>, <gcc@gcc.gnu.org>
Subject: Re: GCC 3.0.4 GCC 3.0.4
Date: Mon, 21 Jan 2002 12:59:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.43.0201211823530.2391-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20020121170420.GA13481@codesourcery.com>
On Mon, 21 Jan 2002, Zack Weinberg wrote:
> How's this? I went back through the change logs and made entries for
> everything since 3.0.3.
Looks fine, thanks!
> + <li>GCC 3.0 now supports <a href="http://www.netbsd.org/">NetBSD</a>
> + 1.5.2 on x86 processors.</li>
Do we support only NetBSD 1.5.2 or 1.5.x or 1.5.2 and higher?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2002-01-21 17:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 1:24 Mark Mitchell
2002-01-21 5:12 ` Zack Weinberg
2002-01-21 5:29 ` Mark Mitchell
2002-01-21 8:00 ` Gerald Pfeifer
2002-01-21 12:30 ` Zack Weinberg
2002-01-21 12:59 ` Gerald Pfeifer [this message]
2002-01-21 13:12 ` Zack Weinberg
2002-01-21 14:08 ` Mark Mitchell
2002-01-21 8:42 ` Zack Weinberg
2002-01-21 7:58 ` Neil Booth
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.43.0201211823530.2391-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=zack@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).