public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Anthony Green <green@redhat.com>,
	Joern Rennecke <joern.rennecke@superh.com>
Cc: tromey@redhat.com, kaz Kojima <kkojima@rr.iij4u.or.jp>,
	gcc-patches@gcc.gnu.org, java@gcc.gnu.org,
	Alexandre Oliva <aoliva@redhat.com>,
	GCC Hackers <gcc@gcc.gnu.org>
Subject: Re: Unreviewed patch
Date: Thu, 12 Jun 2003 15:47:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.55.0306121737160.68914@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <3EE89AEE.452EC932@superh.com>

On Thu, 12 Jun 2003, Anthony Green wrote:
>> I believe we've agreed in the past that port maintainers can make
>> port-specific libffi changes.  So I think you can check in your fix
>> that basis.
> The situation is a little frustrating because it's not made explicit in
> the MAINTAINERS file.  I once tried to clear this up with the SC through
> one of its members, but got no reply.

That's unfortunate.

> My suggestion is that the following people should be able to approve
> libffi changes:
>
> 0. Global maintainers
> 1. GCC port maintainers, since many times they will be the only ones who
> understand the asm code.
> 2. Tromey, as the maintainer of libgcj, since this is an important part
> of it.
> 3. Me, as the original author.
> BTW - I think we should also add MAINTAINERS entries for zlib, boehm-gc
> and fastjar.

Would you mind suggesting appropriate additions to the MAINTAINERS file?
I'll happily forward them to the SC and make sure to follow it.

On Thu, 12 Jun 2003, Joern Rennecke wrote:
> I'm somewhat unsure about the status of libffi.  On the one
> hand it is a separate project, and as such it appears that only
> Anthony Green can approve patches.
> On the other hand the libffi home page says 'libffi is now largely
> maintained as part of GCC.' , and if it is actually maintained as
> part of GCC, that would mean that global and target port maintainers
> of gcc can approve patches.

The point is, is it largely maintained as part of GCC, or is it now
part of GCC (like, for example, libstdc++ and libgcj which became
fully integrated)?

Gerald
-- 
Gerald "Jerry"   pfeifer@dbai.tuwien.ac.at   http://www.pfeifer.com/gerald/

  parent reply	other threads:[~2003-06-12 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200306121332.h5CDWGJ10519@r-rr.iij4u.or.jp>
2003-06-12 14:42 ` Tom Tromey
2003-06-12 15:22   ` Anthony Green
2003-06-12 16:09     ` Joseph S. Myers
2003-06-12 23:19   ` kaz Kojima
     [not found] ` <3EE89AEE.452EC932@superh.com>
2003-06-12 15:47   ` Gerald Pfeifer [this message]
2002-07-25  7:34 Momchil Velikov

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=Pine.BSF.4.55.0306121737160.68914@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=aoliva@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=green@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=joern.rennecke@superh.com \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=tromey@redhat.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).