From: Richard Biener <richard.guenther@gmail.com>
To: Andrew Haley <aph@redhat.com>
Cc: jeremy.bennett@embecosm.com, David Edelsohn <edelsohn@gnu.org>,
GCC Development <gcc@gcc.gnu.org>,
Joern Rennecke <joern.rennecke@embecosm.com>
Subject: Re: Getting the ARC port reviewed and accepted
Date: Tue, 01 Oct 2013 13:30:00 -0000 [thread overview]
Message-ID: <CAFiYyc1q+hEeL5L2bwU_8fMW4SDSYBKdyG-xikRK_cgHF=mAkw@mail.gmail.com> (raw)
In-Reply-To: <524ACD05.2020701@redhat.com>
On Tue, Oct 1, 2013 at 3:24 PM, Andrew Haley <aph@redhat.com> wrote:
> On 10/01/2013 11:32 AM, Richard Biener wrote:
>>
>> Well, I want clarification as of whether assigning maintainership of the
>> port is equivalent to getting approval for checking in the port specific
>> parts. Which_I_ would think is reasonable (for the maintainer being
>> Joern even more so).
>
>
> Well, sure it is. If Joern is the maintainer he don't need anyone else
> to approve his patches to his own port.
Good. So what remains is the configure parts, the libgcc parts and
the documentation parts. Though for all of them they look ARC
specific so maybe the maintainership covers these as well.
I suppose this automatism when being assigned the maintainership
escaped Joern as well ... ;)
Richard.
> Andrew.
>
next prev parent reply other threads:[~2013-10-01 13:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 16:09 Jeremy Bennett
2013-10-01 8:11 ` Richard Biener
2013-10-01 9:10 ` Andrew Haley
2013-10-01 10:32 ` Richard Biener
2013-10-01 13:24 ` Andrew Haley
2013-10-01 13:30 ` Richard Biener [this message]
2013-10-01 14:19 ` Joern Rennecke
2013-10-01 15:23 ` Andrew Haley
2013-10-01 15:29 ` Jeff Law
2013-10-01 23:47 ` David Edelsohn
2013-10-02 8:32 ` Andrew Haley
2013-10-02 12:46 ` David Edelsohn
2013-10-02 13:49 ` Andrew Haley
2013-10-02 13:59 ` Richard Biener
2013-10-02 15:43 ` David Malcolm
2013-10-03 12:24 ` Richard Earnshaw
2013-10-03 7:46 ` Jeremy Bennett
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='CAFiYyc1q+hEeL5L2bwU_8fMW4SDSYBKdyG-xikRK_cgHF=mAkw@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=aph@redhat.com \
--cc=edelsohn@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jeremy.bennett@embecosm.com \
--cc=joern.rennecke@embecosm.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).