From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Can I have some basic BZ perms please?
Date: Sun, 19 Jul 2009 17:17:00 -0000 [thread overview]
Message-ID: <4A635806.1080203@gmail.com> (raw)
Hi team,
I'd like to have some basic BZ perms if I may, so I can help out with
cygwin/win32-related PRs. I'd like to be able to assign bugs to myself (at
least ones that I created myself, depending how fine-grained it is), and
perhaps be allowed to change status on other bugs too (I occasionally run into
already fixed bugs, or bugs waiting for confirmation that I can confirm). Is
there a policy? I'm only a WAA contributor, not a maintainer, but I think I
can generally be trusted to know what I'm doing :)
cheers,
DaveK
next reply other threads:[~2009-07-19 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 17:17 Dave Korn [this message]
2009-07-19 17:20 ` Richard Guenther
2009-07-19 17:52 ` Dave Korn
2009-07-19 17:20 ` Kai Tietz
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=4A635806.1080203@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=gcc@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).