From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Sunrise trusted committers with bugzilla access
Date: Fri, 15 Sep 2006 13:50:31 +0200 [thread overview]
Message-ID: <eee44g$k8t$1@sea.gmane.org> (raw)
In-Reply-To: 20060914210414.GE12566@woodpecker.gentoo.org
Bryan Østergaard wrote:
> As there's been very little, if any, interest from anybody besides
> Stefan and Recruiters / Developer Relations I'm going to deny the
> contributor access idea. Recruiters and Developer Relations feels that
> this is a bad idea, especially seeing how hard it has been to reach any
> kind of resolution regarding who should get access and how we should
> solve the problems that I've outlined earlier.
thanks for the clear no. I should have realized that before writing the GLEP
and everything. Sorry :(
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2006-09-15 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 21:39 [gentoo-dev] Sunrise trusted committers with bugzilla access Stefan Schweizer
2006-09-14 16:53 ` Simon Stelling
2006-09-14 21:04 ` Bryan Østergaard
2006-09-15 3:03 ` Mike Frysinger
2006-09-15 11:50 ` Stefan Schweizer [this message]
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='eee44g$k8t$1@sea.gmane.org' \
--to=genstef@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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