From: larsbj@gullik.net (Lars Gullik Bjønnes)
To: Janis Johnson <janis187@us.ibm.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>, gcc@gcc.gnu.org
Subject: Re: boost archive used for testing
Date: Wed, 02 Apr 2003 20:45:00 -0000 [thread overview]
Message-ID: <m3smt0bvig.fsf@tyfon.gullik.net> (raw)
In-Reply-To: <20030402091639.A1390@us.ibm.com>
Janis Johnson <janis187@us.ibm.com> writes:
| There are several versions and formats to choose from at SourceForge.
| Should we recommend a particular version for GCC integration testing
| and if so, which one? (That question is for people familiar with
| Boost.)
The last released one, 1.30.0 currently.
--
Lgb
prev parent reply other threads:[~2003-04-02 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 13:50 Gerald Pfeifer
2003-04-02 17:57 ` Janis Johnson
2003-04-02 20:14 ` Janis Johnson
2003-04-02 20:46 ` Gerald Pfeifer
2003-04-02 21:34 ` Janis Johnson
2003-04-02 20:45 ` Lars Gullik Bjønnes [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=m3smt0bvig.fsf@tyfon.gullik.net \
--to=larsbj@gullik.net \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).