From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: formally allow qa to suspend commit rights
Date: Sun, 19 Jan 2014 17:24:30 -0800 [thread overview]
Message-ID: <CAAr7Pr-1GsHbL5zzyS5u-N8QsR+Qf-tKev2N-O4k94AgWHY8_A@mail.gmail.com> (raw)
In-Reply-To: <20140119050224.GA7898@laptop.home>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
On Sat, Jan 18, 2014 at 9:02 PM, William Hubbs <williamh@gentoo.org> wrote:
> All,
>
> I would like to bring back for discussion an old patch to glep 48 [1]
> which was suggested by Jorge [2].
>
> That patch evolved into this one [3], and in the council meeting back
> then [4], parts of it made their way into glep 48, but the rest seemed to
> be forgotten.
>
> Attached you will find an updated version of this patch taking into
> account the current version of glep 48.
>
> This is nothing new; the qa team has requested that commit rights be
> suspended before. I am just proposing that we actually add the parts of
> the old patch to the glep that spell out when and how this can happen.
>
> Thoughts?
>
We almost never suspend commit rights. I'm not really finding a situation
where this is necessary. Certainly not in the streamlined fashion proposed
here.
-A
>
> William
>
> [1] http://wiki.gentoo.org/wiki/GLEP:48
> [2]
> http://archives.gentoo.org/gentoo-project/msg_ac161677a6e06a8647e16420eeae8d47.xml
> [3] http://www.mail-archive.com/gentoo-qa@lists.gentoo.org/msg00144.html
> [4]
> http://www.gentoo.org/proj/en/council/meeting-logs/20110608-summary.txt
>
[-- Attachment #2: Type: text/html, Size: 2116 bytes --]
next prev parent reply other threads:[~2014-01-20 1:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 5:02 [gentoo-dev] rfc: formally allow qa to suspend commit rights William Hubbs
2014-01-19 5:07 ` William Hubbs
2014-01-19 5:17 ` [gentoo-dev] " W. Trevor King
2014-01-19 12:46 ` [gentoo-dev] " hasufell
2014-01-20 1:05 ` Tom Wijsman
2014-01-19 20:22 ` Denis Dupeyron
2014-01-20 1:01 ` Tom Wijsman
2014-01-20 1:22 ` Denis Dupeyron
2014-01-20 2:47 ` Tom Wijsman
2014-01-22 16:30 ` Jeroen Roovers
2014-01-20 1:24 ` Alec Warner [this message]
2014-01-20 2:54 ` Tom Wijsman
2014-01-20 13:59 ` Rich Freeman
2014-01-20 14:09 ` Alan McKinnon
2014-01-21 0:22 ` Patrick Lauer
2014-01-21 0:46 ` Rich Freeman
2014-01-21 5:29 ` Alec Warner
2014-01-21 5:27 ` Alec Warner
2014-01-22 17:54 ` Ciaran McCreesh
2014-01-22 22:37 ` Andreas K. Huettel
2014-01-22 22:59 ` Tom Wijsman
2014-01-21 14:56 ` Tom Wijsman
2014-01-21 15:47 ` Rich Freeman
2014-01-21 17:26 ` William Hubbs
2014-01-21 17:50 ` Rich Freeman
2014-01-21 17:56 ` Peter Stuge
2014-01-21 18:11 ` Tom Wijsman
2014-01-21 18:16 ` Peter Stuge
2014-01-21 19:18 ` Tom Wijsman
2014-01-21 21:03 ` Thomas Sachau
2014-01-21 22:56 ` Tom Wijsman
2014-01-21 23:14 ` William Hubbs
2014-01-22 7:00 ` Alan McKinnon
2014-01-22 10:36 ` hasufell
2014-01-22 10:39 ` hasufell
2014-01-22 10:58 ` Alec Warner
2014-01-22 23:29 ` Tom Wijsman
2014-01-22 12:34 ` Patrick Lauer
2014-01-22 19:42 ` Rich Freeman
2014-01-22 23:40 ` Tom Wijsman
2014-01-22 22:06 ` Alan McKinnon
2014-01-22 23:15 ` Tom Wijsman
2014-01-21 23:20 ` hasufell
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=CAAr7Pr-1GsHbL5zzyS5u-N8QsR+Qf-tKev2N-O4k94AgWHY8_A@mail.gmail.com \
--to=antarus@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