From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: "Pekka Jääskeläinen" <pekka@parmance.com>,
"Martin Jambor" <mjambor@suse.cz>,
overseers@gcc.gnu.org
Subject: Re: svn/cvs access
Date: Sun, 29 Jan 2017 19:23:00 -0000 [thread overview]
Message-ID: <20170129192342.GB7080@ednor.casa.cgf.cx> (raw)
In-Reply-To: <CAJk11WCZw88gR1DjftYXGrhbqpxTtgsGEJm0oCp2oJCEhQSdfA@mail.gmail.com>
On Fri, Jan 27, 2017 at 03:14:39PM +0200, Pekka Jääskeläinen wrote:
>Dear gcc overseers,
>
>I recently applied for svn/cvs commit access due to my new BRIG FE maintenance
>status.
>
>Is there any estimate regarding if it is granted and how long it might
>take to receive it?
Your request did not have a proper approver. You used "jamborn@gcc.gnu.org" who
is listed in the MAINTAINERS file only as a write-after-approval submitter.
next prev parent reply other threads:[~2017-01-29 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 13:15 Pekka Jääskeläinen
2017-01-29 19:23 ` Christopher Faylor [this message]
2017-01-29 22:35 ` Gerald Pfeifer
2017-01-30 8:45 ` Martin Jambor
2017-01-30 19:14 ` Christopher Faylor
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=20170129192342.GB7080@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=mjambor@suse.cz \
--cc=overseers@gcc.gnu.org \
--cc=pekka@parmance.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).