From: Sebastien Bourdeauducq <sebastien@milkymist.org>
To: overseers@gcc.gnu.org
Cc: green@moxielogic.com
Subject: Bug database write permissions
Date: Tue, 01 Feb 2011 13:38:00 -0000 [thread overview]
Message-ID: <1296567357.15319.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20110130180606.26118.qmail@sourceware.org>
Hi,
On Sun, 2011-01-30 at 18:06 +0000, root@sourceware.org wrote:
> Your account is now active, the login name is lekernel@gcc.gnu.org.
(...)
> You have been assigned edit rights to the gcc Bugzilla bug reporting
> database.
There seems to be some problem with that, as I cannot edit bug reports
and the "Permissions" tab in my account settings says "There are no
permission bits set on your account.". Could you help me with this
issue?
The subversion write access works correctly.
Thank you,
Sébastien
next parent reply other threads:[~2011-02-01 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110130180606.26118.qmail@sourceware.org>
2011-02-01 13:38 ` Sebastien Bourdeauducq [this message]
2011-02-01 14:23 ` Ian Lance Taylor
2011-02-01 18:00 ` Frédéric Buclin
2011-02-01 19:11 ` Sebastien Bourdeauducq
2011-02-01 19:25 ` Frédéric Buclin
2011-02-01 19:50 ` Sebastien Bourdeauducq
2011-02-01 20:14 ` Frédéric Buclin
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=1296567357.15319.4.camel@localhost.localdomain \
--to=sebastien@milkymist.org \
--cc=green@moxielogic.com \
--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).