From: Mark Mitchell <mark@codesourcery.com>
To: gcc mailing list <gcc@gcc.gnu.org>
Cc: Giovanni Bajo <rasky@develer.com>
Subject: Management of new ports
Date: Thu, 04 Aug 2005 20:05:00 -0000 [thread overview]
Message-ID: <42F2750A.808@codesourcery.com> (raw)
Giovanni --
On July 12th, you posted:
http://gcc.gnu.org/ml/gcc/2005-07/msg00483.html
asking about handing of new ports.
The SC has discussed the issue, at your request. Fundamentally, the SC
feels that this issue is outside its purview as a "board of directors"
for GCC; this is an issue for the technical management of GCC (i.e.,
maintainers) to decide.
Other than that conclusion, the rest of this email is just my summary
and opinion, not an official SC statement. Where I say "we" I'm talking
about my perception of an informal consensus of people that participated
in the discussion, not an official dictate.
In general, we think that wall new ports with active maintainership
sould be accepted, if the ports meet our technical criteria. However,
we also recognize that reviewing new ports is hard, and time-consuming,
and that reviewers are volunteers, and so that may not happen very
quickly. We are not in favor of "auto approval".
You mentioned that you submitted a patch to update the technical
requirements for ports to say that cc0 ports would not be accepted, etc.
Personally, I think that's entirely appropriate. The SC doesn't want
to be involved in making such a list, or approving it; that should be
done by consensus of the maintainers. But, this conclusion should
remove the objection that "there is no official statement on this". You
should probably also mark the appropriate macros, etc., in the internals
document as deprecated.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
reply other threads:[~2005-08-04 20:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42F2750A.808@codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=rasky@develer.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).