From: Mark Wielaard <mark@klomp.org>
To: Jonathan Wakely via Overseers <overseers@sourceware.org>
Cc: Jonathan Wakely <jwakely@redhat.com>,
overseers@gcc.gnu.org, Fangrui Song <maskray@google.com>
Subject: Re: Authenticated access for gcc
Date: Fri, 16 Feb 2024 13:45:18 +0100 [thread overview]
Message-ID: <b5c28a06a505bb39ea0a2d1f70e4b996542cd09c.camel@klomp.org> (raw)
In-Reply-To: <CACb0b4kpgATebNRk1gwfyXzGGSrm8ADq5D_7XC69gPaCS5TCzA@mail.gmail.com>
On Fri, 2024-02-16 at 10:51 +0000, Jonathan Wakely via Overseers wrote:
> On Fri, 16 Feb 2024 at 10:28, Mark Wielaard <mark@klomp.org> wrote:
> > On Wed, Feb 14, 2024 at 11:02:16AM -0800, Fangrui Song via Overseers wrote:
> > > I am following https://gcc.gnu.org/gitwrite.html here to request GCC
> > > write-after-approval access (username: maskray).
> >
> > Note that page should tell you to contact admin-requests@sourceware.org
> > (overseers is a public list for generic infrastructure discussions,
> > admin-requests a private list for account issues).
> >
> > > Jonathan Wakely has agreed to be the sponsor.
> >
> > Good, and CCed. If Jonathan could ack we'll make it happen.
>
> Please go ahead, I'm happy to sponsor Fangrui.
Great. Welcome Fangrui! You have been added to the gcc group.
Everything should work as is just with s/sourceware.org/gcc.gnu.org/ in
your settings when working with the gcc project. See
also https://gcc.gnu.org/gitwrite.html#account and
https://sourceware.org/sourceware/accountinfo.html
Cheers,
Mark
next prev parent reply other threads:[~2024-02-16 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 19:02 Fangrui Song
2024-02-16 10:22 ` Mark Wielaard
2024-02-16 10:51 ` Jonathan Wakely
2024-02-16 12:45 ` Mark Wielaard [this message]
2024-02-16 18:46 ` Fangrui Song
2024-02-18 18:10 ` Gerald Pfeifer
2024-02-19 7:35 ` Fangrui Song
2024-02-19 9:44 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2024-01-11 3:57 Fangrui Song
2024-01-11 11:34 ` Frank Ch. Eigler
2024-01-11 18:46 ` Fangrui Song
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=b5c28a06a505bb39ea0a2d1f70e4b996542cd09c.camel@klomp.org \
--to=mark@klomp.org \
--cc=jwakely@redhat.com \
--cc=maskray@google.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).