public inbox for
 help / color / mirror / Atom feed
From: Tsukasa OI <>
To:, Tsukasa OI <>
Cc: Kito Cheng <>
Subject: Request: Authenticated access to GCC
Date: Tue, 29 Aug 2023 18:46:34 +0900	[thread overview]
Message-ID: <> (raw)

To GCC Overseers,

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

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 ( 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

Sponsor: Kito Cheng
Sponsor Mail:
Sponsor Position: CPU port maintainer, RISC-V


             reply	other threads:[~2023-08-29  9:46 UTC|newest]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).