public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Tsukasa OI via Overseers <overseers@sourceware.org>,
	Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: Kito Cheng <kito.cheng@gmail.com>
Subject: Re: Request: Authenticated access to GCC
Date: Tue, 29 Aug 2023 13:10:38 +0200	[thread overview]
Message-ID: <53c73e8b8103de8f2dd850a48c49262a07260f4a.camel@klomp.org> (raw)
In-Reply-To: <b29c33af-3b06-4293-baa9-2c0c5984b509@irq.a4lg.com>

Hi Tsukasa,

Note, we do have a new separate (private)
account-requests@sourceware.org address now for account requests.

On Tue, 2023-08-29 at 18:46 +0900, Tsukasa OI via Overseers wrote:
> I am Tsukasa OI, a contributor to Binutils / GDB / GCC and a
> write-after-approval committer to Binutils / GDB.  While I'm relatively
> new to GCC contribution, I am actively working on the RISC-V-related
> changes.
> 
> To make contributions much more flexibly (e.g. choosing the right patch
> set version / time to commit from the contributor), I hereby request the
> authorized write access (write after approval) to GCC project.
> 
> Account (sourceware.org): a4lg
> Name (First/Last): Tsukasa Oi
> (I think I registered the name as "Oi" but might be capitalized "OI").
> Copyright for GCC contribution: Assigned to FSF
> Mail: research_trasio@irq.a4lg.com
> 
> Sponsor: Kito Cheng
> Sponsor Mail: kito.cheng@gmail.com
> Sponsor Position: CPU port maintainer, RISC-V

That all checks out and I also found
https://inbox.sourceware.org/gcc-patches/CA+yXCZC7yGCgXo3_U4Y8wtO8QXNk9dA4Ga4v_eEhthPc0DMA-A@mail.gmail.com/

You are now a member of the gcc group.
Please follow https://gcc.gnu.org/gitwrite.html and add yourself to the
MAINTAINERS file under Write After Approval.

Cheers,

Mark

  reply	other threads:[~2023-08-29 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29  9:46 Tsukasa OI
2023-08-29 11:10 ` Mark Wielaard [this message]
2023-08-29 11:15   ` Mark Wielaard

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=53c73e8b8103de8f2dd850a48c49262a07260f4a.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=kito.cheng@gmail.com \
    --cc=overseers@sourceware.org \
    --cc=research_trasio@irq.a4lg.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).