From: mike stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, mark@codesourcery.com
Subject: Re: Important: Development Plan for Future Releases
Date: Tue, 17 Jul 2001 09:03:00 -0000 [thread overview]
Message-ID: <200107171602.JAA03289@kankakee.wrs.com> (raw)
> Date: Mon, 16 Jul 2001 20:43:30 -0700
> From: Mark Mitchell <mark@codesourcery.com>
> To: gcc@gcc.gnu.org
> The Steering Committee has, after much deliberation, and after
> considering the various opinions presented on the public mailing
> lists, adopted the proposal detailed below. This policy will
> govern the development of GCC henceforth; it is important that
> all developers understand the policy.
Policy exists as documentation on a web site, announcement of policy
references that policy on the web site, this should be policy.
:-)
next reply other threads:[~2001-07-17 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 9:03 mike stump [this message]
2001-07-17 16:01 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
2001-07-19 3:55 Richard Kenner
2001-07-16 21:03 Mark Mitchell
2001-07-17 0:51 ` Joseph S. Myers
2001-07-17 4:02 ` Gerald Pfeifer
2001-07-17 4:11 ` Geoff Keating
2001-07-18 9:26 ` Gerald Pfeifer
2001-07-17 8:57 ` Anthony Green
2001-07-17 11:08 ` Mark Mitchell
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=200107171602.JAA03289@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@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).