From: Gerald Pfeifer <gerald@pfeifer.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>
Cc: DJ Delorie <dj@redhat.com>, gcc@gcc.gnu.org
Subject: Re: Ping: New Toshiba Media Processor (mep-elf) port and maintainer
Date: Sat, 20 Jun 2009 17:36:00 -0000 [thread overview]
Message-ID: <alpine.LSU.1.99.0906201936200.29901@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20090619001416.GA7995@hungry-tiger.westford.ibm.com>
On Thu, 18 Jun 2009, Michael Meissner wrote:
> All of my comments about the internals of the mep would be things to do
> if you desired, but as port maintainer, I don't see that we have to
> apply standards set for the rest of the compiler (if we did, probably
> half of the ports would be rejected for formatting in some of the
> files).
I believe what was mentioned at the Summit was that where ports introduce
deprecated interfaces or possibly increase the maintainence burden for
other maintainers in the future that is something we want to avoid, and
for that reason a check of port beyond changes in common code is
beneficial.
Gerald
prev parent reply other threads:[~2009-06-20 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 15:18 Gerald Pfeifer
2009-06-05 15:51 ` DJ Delorie
2009-06-08 22:52 ` DJ Delorie
2009-06-17 4:52 ` Ping: " DJ Delorie
2009-06-19 0:14 ` Michael Meissner
2009-06-19 1:32 ` DJ Delorie
2009-06-20 17:36 ` Gerald Pfeifer [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=alpine.LSU.1.99.0906201936200.29901@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.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).