From: Fangrui Song <maskray@google.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: overseers@sourceware.org, jwakely@redhat.com
Subject: Re: Authenticated access for gcc
Date: Sun, 18 Feb 2024 23:35:16 -0800 [thread overview]
Message-ID: <CAFP8O3KgCp3-LX=DB-P2cVzS_-GanABHKxyBCPV=br7Js6+8tg@mail.gmail.com> (raw)
In-Reply-To: <d414c594-1b69-fb5a-136c-103e9eccf2f8@pfeifer.com>
On Sun, Feb 18, 2024 at 10:10 AM Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Fri, 16 Feb 2024, Mark Wielaard via Overseers 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).
>
> It actually does that since the following commit to the GCC web pages:
>
> commit 1e8d94c15d64796ba2ea5abadc3b5e48ff964801
> Author: Frank Ch. Eigler <fche@elastic.org>
> Date: Thu Jan 11 06:40:05 2024 -0500
>
> tweak for sourceware account request alias
>
> Fangrui (and anyone else): is there a stale reference to overseers@ that
> we have been missing?
>
> Gerald
Hi Gerald,
I think the documentation is up-to-date. I see that the commit
https://gcc.gnu.org/cgit/gcc-wwwdocs/commit/?id=1e8d94c15d64796ba2ea5abadc3b5e48ff964801
updated https://gcc.gnu.org/gitwrite.html
I used overseers@ by mistake as overseers@sourceware.org has been deep
in my mind... Sorry for the confusion I caused.
next prev parent reply other threads:[~2024-02-19 7:35 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
2024-02-16 18:46 ` Fangrui Song
2024-02-18 18:10 ` Gerald Pfeifer
2024-02-19 7:35 ` Fangrui Song [this message]
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='CAFP8O3KgCp3-LX=DB-P2cVzS_-GanABHKxyBCPV=br7Js6+8tg@mail.gmail.com' \
--to=maskray@google.com \
--cc=gerald@pfeifer.com \
--cc=jwakely@redhat.com \
--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).