From: ludo@gnu.org (Ludovic Courtès)
To: overseers@gcc.gnu.org
Cc: Thomas Schwinge <thomas@codesourcery.com>
Subject: Access to the GCC repository
Date: Mon, 22 Jun 2015 08:27:00 -0000 [thread overview]
Message-ID: <87616gw3jx.fsf@gnu.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 34 bytes --]
A friendly ping...
Ludo’.
[-- Attachment #1.2: Type: message/rfc822, Size: 2036 bytes --]
[-- Attachment #1.2.1.1: Type: text/plain, Size: 240 bytes --]
Hello,
Thomas Schwinge (Cc’d) has agreed to sponsor me for write-after-approval
access to the GCC repository.
My sourceware.org account is ‘ludo’. Could you grant me access to the
repository?
Thanks in advance,
Ludo’.
[-- Attachment #1.2.1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next reply other threads:[~2015-06-22 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 8:27 Ludovic Courtès [this message]
2015-06-22 10:16 ` Thomas Schwinge
2015-06-22 11:39 ` Frank Ch. Eigler
2015-06-23 7:56 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2019-06-11 17:27 Matthew Beliveau
2019-06-11 17:36 ` Matthew Beliveau
2015-06-05 8:05 Ludovic Courtès
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=87616gw3jx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=overseers@gcc.gnu.org \
--cc=thomas@codesourcery.com \
/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).