From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org, Fangrui Song <maskray@google.com>
Subject: Re: Authenticated access for gcc
Date: Thu, 11 Jan 2024 06:34:35 -0500 [thread overview]
Message-ID: <20240111113435.GG28684@redhat.com> (raw)
In-Reply-To: <CAFP8O3K+J+X+fPPoDd4XxhBUVLaPQCCDO9f+Zynac=+wcdDhrQ@mail.gmail.com>
Hi -
> I am following https://gcc.gnu.org/gitwrite.html here to request GCC
> access (username: maskray) so that I can land approved changes of mine
> by myself. [...]
GCC commit access must be sponsored by an existing GCC maintainer.
https://gcc.gnu.org/gitwrite.html#authenticated
- FChE
next prev parent reply other threads:[~2024-01-11 11:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 3:57 Fangrui Song
2024-01-11 11:34 ` Frank Ch. Eigler [this message]
2024-01-11 18:46 ` Fangrui Song
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
2024-02-19 9:44 ` 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=20240111113435.GG28684@redhat.com \
--to=fche@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).