From: Steven Bosscher <stevenb@suse.de>
To: "Aaron W. LaFramboise" <aaronavay62@aaronwl.com>,
Dan Kegel <dank@kegel.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
Giovanni Bajo <giovannibajo@libero.it>
Subject: Re: Request for Steering Committee: official release criteria for 4.x
Date: Sun, 31 Oct 2004 20:49:00 -0000 [thread overview]
Message-ID: <200410311220.51442.stevenb@suse.de> (raw)
In-Reply-To: <4184797E.4000907@aaronwl.com>
On Sunday 31 October 2004 06:34, Aaron W. LaFramboise wrote:
> Is there any way for Joe GCC User to get a copy of SPEC? Or is SPEC
> proprietary or secret or otherwise non-free?
SPEC is not free.
Gr.
Steven
next prev parent reply other threads:[~2004-10-31 10:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 15:21 Dan Kegel
2004-10-31 18:22 ` Aaron W. LaFramboise
2004-10-31 20:49 ` Steven Bosscher [this message]
2004-10-31 23:03 ` Dan Kegel
2004-11-01 11:30 ` Request for Steering Committee: official release criteria for4.x Giovanni Bajo
2004-11-01 21:48 ` Request for Steering Committee: official release criteria for 4.x Jeffrey A Law
2004-11-01 22:25 ` Vladimir Makarov
-- strict thread matches above, loose matches on Subject: below --
2004-10-30 14:17 Giovanni Bajo
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=200410311220.51442.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=aaronavay62@aaronwl.com \
--cc=dank@kegel.com \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
/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).