public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: Alexander Fomin <afomin.mailbox@gmail.com>,
	overseers@gcc.gnu.org,  Kirill Yukhin <kirill.yukhin@gmail.com>
Subject: Re: GCC SVN write after approval access request
Date: Thu, 08 Oct 2015 16:06:00 -0000	[thread overview]
Message-ID: <CAFULd4Y0FUueJ8e=q++g9gnrhxGHAZ4-vOsftND2w3YOGNi6iw@mail.gmail.com> (raw)
In-Reply-To: <m3wpuxqu1p.fsf@pepe.airs.com>

On Thu, Oct 8, 2015 at 5:06 PM, Ian Lance Taylor <ian@airs.com> wrote:
> Alexander Fomin <afomin.mailbox@gmail.com> writes:
>
>> I'm currently working on AVX512 extensions machine description
>> refinement for i386 targets.
>> I've already submitted two patches that have been successfully approved
>> by i386 vector ISA extensions maintainer Kirill Yukhin and checked in
>> (r228010, r228525). There have been no serious concerns from i386 port
>> maintainer Uros Bizjak as well.
>> As this activity will be continued, I'd like to obtain write after
>> approval SVN access.
>> Please let me know whether it's possible.
>
> You need to be sponsored by a GCC maintainer (such as Uros).  When
> someone supports you, we can add your existing account to the gcc group.

While I don't oppose the nomination, I think that the correct sponsor
is Kirill, since Alexander plans to work in AVX512 part of the x86
target. We do have special maintainer for x86 ISA extensions, as is
already documented in MAINTAINERS.

BR,
Uros.

  reply	other threads:[~2015-10-08 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08 15:06 Alexander Fomin
2015-10-08 15:56 ` Ian Lance Taylor
2015-10-08 16:06   ` Uros Bizjak [this message]
2015-10-09  3:46     ` Kirill Yukhin
2015-10-21 14:29       ` Ian Lance Taylor

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='CAFULd4Y0FUueJ8e=q++g9gnrhxGHAZ4-vOsftND2w3YOGNi6iw@mail.gmail.com' \
    --to=ubizjak@gmail.com \
    --cc=afomin.mailbox@gmail.com \
    --cc=ian@airs.com \
    --cc=kirill.yukhin@gmail.com \
    --cc=overseers@gcc.gnu.org \
    /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).