public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Cupertino Miranda via Overseers <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org,
	Cupertino Miranda <cupertino.miranda@oracle.com>,
	jose.marchesi@oracle.com
Subject: Re: Request access to GCC repository.
Date: Fri, 21 Jul 2023 19:15:34 +0200	[thread overview]
Message-ID: <20230721171534.GA10937@gnu.wildebeest.org> (raw)
In-Reply-To: <87wmyt45ub.fsf@oracle.com>

Hi Cupertino,

On Fri, Jul 21, 2023 at 04:55:24PM +0100, Cupertino Miranda via Overseers wrote:
> Please consider this email as my request to get write-after-approval for GCC.
> I have write access in binutils.
> My login is cupermir.
> 
> My sponsor is: Jose Marchesi <jose.marchesi@oracle.com>

Welcome! Saw your work on the BPF pseudo-c syntax. Nice.
Added you to the gcc group.

Cheers,

Mark

      reply	other threads:[~2023-07-21 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 15:55 Cupertino Miranda
2023-07-21 17:15 ` Mark Wielaard [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=20230721171534.GA10937@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=cupertino.miranda@oracle.com \
    --cc=jose.marchesi@oracle.com \
    --cc=overseers@gcc.gnu.org \
    --cc=overseers@sourceware.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).