public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Kirill Yukhin <kirill.yukhin@gmail.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
	Alexander Fomin <afomin.mailbox@gmail.com>,
	overseers@gcc.gnu.org
Subject: Re: GCC SVN write after approval access request
Date: Wed, 21 Oct 2015 14:29:00 -0000	[thread overview]
Message-ID: <m3fv1kr9fe.fsf@pepe.airs.com> (raw)
In-Reply-To: <20151008160531.GA14795@msticlxl57.ims.intel.com> (Kirill Yukhin's message of "Thu, 8 Oct 2015 19:05:34 +0300")

Kirill Yukhin <kirill.yukhin@gmail.com> writes:

> Hi folks!
> On 08 Oct 17:56, Uros Bizjak wrote:
>> On Thu, Oct 8, 2015 at 5:06 PM, Ian Lance Taylor <ian@airs.com> wrote:
>> > Alexander Fomin <afomin.mailbox@gmail.com> writes:
>> >> 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.
>
> I am OK.

I've added Alexander to the gcc group on sourceware.

Alexander, please add yourself to the write-after-approve list in
gcc/MAINTAINERS.

Ian

      reply	other threads:[~2015-10-09  3:46 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
2015-10-09  3:46     ` Kirill Yukhin
2015-10-21 14:29       ` Ian Lance Taylor [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=m3fv1kr9fe.fsf@pepe.airs.com \
    --to=ian@airs.com \
    --cc=afomin.mailbox@gmail.com \
    --cc=kirill.yukhin@gmail.com \
    --cc=overseers@gcc.gnu.org \
    --cc=ubizjak@gmail.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).