From: Hafiz Abid Qadeer <abid_qadeer@mentor.com>
To: <overseers@sourceware.org>
Subject: Write access for gcc
Date: Fri, 9 Apr 2021 15:25:13 +0100 [thread overview]
Message-ID: <47b39c87-e80a-1050-d4b5-5dc6fbe87a28@mentor.com> (raw)
Hi,
I was advised to request write access for gcc git in:
https://gcc.gnu.org/pipermail/gcc-patches/2021-April/567816.html
After filling form, I was told that my login already exist on the
system. Can you kindly also give me access on gcc.
Thanks,
--
Hafiz Abid Qadeer
Mentor, a Siemens Business
next reply other threads:[~2021-04-09 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 14:25 Hafiz Abid Qadeer [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-09 14:25 Hafiz Abid Qadeer
2021-04-10 19:05 ` Christopher Faylor
2006-08-12 16:53 Write access for GCC Philipp Thomas
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=47b39c87-e80a-1050-d4b5-5dc6fbe87a28@mentor.com \
--to=abid_qadeer@mentor.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).