From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@gcc.gnu.org, Antoniu Pop <antoniu.pop@mines-paristech.fr>
Subject: Re: SVN write access for Cupertino Miranda
Date: Mon, 27 Sep 2010 13:01:00 -0000 [thread overview]
Message-ID: <20100927130124.GB18236@ednor.casa.cgf.cx> (raw)
In-Reply-To: <AANLkTi=74K8rNVHPyimigTvj8tSLWVV-UPQ5S5S674Fc@mail.gmail.com>
On Mon, Sep 27, 2010 at 10:43:35AM +0200, Antoniu Pop wrote:
>I have approved the write access request of Cupertino Miranda, but he
>is still unable to access the SVN after roughly one week.
>For now, he will exclusively be contributing to the "omp-stream"
>branch with write-after-approval rights.
According to the GCC maintainers file, you do not have approval rights
for this since you are listed as having "Write After Approval"
privileges. You need to be a maintainer to approve SVN access.
cgf
next prev parent reply other threads:[~2010-09-27 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 8:43 Antoniu Pop
2010-09-27 13:01 ` Christopher Faylor [this message]
2010-09-27 14:00 ` Antoniu Pop
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=20100927130124.GB18236@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=antoniu.pop@mines-paristech.fr \
--cc=overseers@gcc.gnu.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).