From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: robo-stable bugs
Date: Thu, 23 May 2013 23:40:42 -0600 [thread overview]
Message-ID: <20130523234042.26eaac89@caribou.gateway.2wire.net> (raw)
In-Reply-To: 20130522105826.69a27217@TOMWIJ-GENTOO
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Wed, 22 May 2013 10:58:26 +0200
Tom Wijsman <TomWij@gentoo.org> wrote:
> On Tue, 21 May 2013 18:57:20 -0600
> Ryan Hill <dirtyepic@gentoo.org> wrote:
> > > Also, your script does not set the STABLEREQ keyword. People are
> > > having to hunt down your robo-stabilisation requests and add it
> > > themselves. You should just do it yourself or turn your script off.
> >
> > Did you read the message? The point is you're supposed to add that
> > yourself. It's not a STABLEREQ until you add arches.
>
> Yet the base system lead went and apply it to any stabilization bug; as
> both him and Jer (the bug wrangling lead) do it this way, I'll be doing
> it as well. Let's not be inconsistent with our leads unless there is
> a wide decision to do so
Okay, so what are you using the STABLEREQ keyword for that you want to set it
when the bug is filed but before archs are added? If you want to see only
stabilization bugs you can search in the Keywording and Stabilization
component. Can you suggest another way to search for stabilization bugs that
don't yet have archs CC'd (which is something I find rather useful)?
--
Ryan Hill psn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-05-24 5:30 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-470392-23709@http.bugs.gentoo.org/>
2013-05-19 13:40 ` [gentoo-dev] robo-stable bugs Jeroen Roovers
2013-05-19 14:35 ` [gentoo-dev] " Michael Palimaka
2013-05-19 15:51 ` [gentoo-dev] " Dirkjan Ochtman
2013-05-19 15:58 ` Markos Chandras
2013-05-19 20:22 ` Andreas K. Huettel
2013-05-20 0:00 ` "Paweł Hajdan, Jr."
2013-05-20 12:10 ` Gilles Dartiguelongue
2013-05-20 16:58 ` "Paweł Hajdan, Jr."
2013-07-27 19:29 ` "Paweł Hajdan, Jr."
2013-07-27 20:16 ` Andreas K. Huettel
2013-05-21 12:21 ` Thomas Sachau
2013-05-21 12:35 ` Chí-Thanh Christopher Nguyễn
2013-05-21 13:32 ` Thomas Sachau
2013-05-22 14:44 ` Jeroen Roovers
2013-05-21 13:20 ` Markos Chandras
2013-05-21 13:38 ` Thomas Sachau
2013-05-21 18:32 ` "Paweł Hajdan, Jr."
2013-05-21 19:51 ` Markos Chandras
2013-05-21 20:17 ` Alexis Ballier
2013-05-21 20:46 ` "Paweł Hajdan, Jr."
2013-05-21 21:37 ` Andreas K. Huettel
2013-05-21 22:25 ` Alexis Ballier
2013-05-22 0:50 ` [gentoo-dev] " Ryan Hill
2013-05-21 23:28 ` [gentoo-dev] " Thomas Sachau
2013-05-21 21:38 ` Andreas K. Huettel
2013-05-22 9:22 ` vivo75
2013-05-22 9:43 ` [gentoo-dev] " Michael Palimaka
2013-05-22 10:07 ` vivo75
2013-05-22 10:12 ` Michael Palimaka
2013-05-22 10:41 ` Thomas Sachau
2013-05-22 11:06 ` Michael Palimaka
2013-05-22 11:16 ` vivo75
2013-05-22 13:03 ` Ian Stakenvicius
2013-05-22 14:51 ` Jeroen Roovers
2013-05-22 15:08 ` Ian Stakenvicius
2013-05-22 13:02 ` Ian Stakenvicius
2013-05-22 13:21 ` [gentoo-dev] " Rich Freeman
2013-05-21 21:22 ` Rick "Zero_Chaos" Farina
2013-05-21 23:43 ` Thomas Sachau
2013-05-21 23:51 ` Andreas K. Huettel
2013-05-22 3:46 ` Rick "Zero_Chaos" Farina
2013-05-22 13:11 ` Ian Stakenvicius
2013-05-22 23:03 ` Rick "Zero_Chaos" Farina
2013-05-23 12:57 ` Ian Stakenvicius
2013-05-23 18:11 ` [gentoo-dev] robo-stable bugs, the flipside Ian Stakenvicius
2013-05-23 18:40 ` Markos Chandras
2013-05-23 18:49 ` Ian Stakenvicius
2013-05-23 19:29 ` Rich Freeman
2013-05-24 13:04 ` Ian Stakenvicius
2013-05-23 20:14 ` Markos Chandras
2013-05-24 13:03 ` Ian Stakenvicius
2013-05-22 12:53 ` [gentoo-dev] robo-stable bugs Ian Stakenvicius
2013-05-22 12:55 ` Michael Mol
2013-05-22 15:00 ` Jeroen Roovers
2013-05-22 15:14 ` Michael Mol
2013-05-22 15:22 ` Ian Stakenvicius
2013-05-20 15:29 ` Tom Wijsman
2013-05-20 17:15 ` Rich Freeman
2013-05-20 18:21 ` Tom Wijsman
2013-05-21 0:46 ` [gentoo-dev] " Duncan
2013-05-22 15:21 ` Jeroen Roovers
2013-05-23 6:22 ` Duncan
2013-05-20 18:00 ` [gentoo-dev] " Robin H. Johnson
2013-05-20 18:29 ` Tom Wijsman
2013-05-29 9:21 ` Michael Weber
2013-05-22 15:03 ` Jeroen Roovers
2013-05-22 15:27 ` Tom Wijsman
2013-05-22 0:57 ` [gentoo-dev] " Ryan Hill
2013-05-22 8:58 ` Tom Wijsman
2013-05-22 9:07 ` Ulrich Mueller
2013-05-22 11:00 ` Tom Wijsman
2013-05-22 11:07 ` Michael Palimaka
2013-05-22 12:02 ` Tom Wijsman
2013-05-24 5:20 ` Ryan Hill
2013-05-24 5:26 ` Tom Wijsman
2013-05-22 9:18 ` Michael Palimaka
2013-05-22 14:56 ` Tom Wijsman
2013-05-22 15:45 ` Jeroen Roovers
2013-05-24 5:40 ` Ryan Hill [this message]
2013-05-24 5:58 ` Tom Wijsman
2013-05-27 10:54 ` Jeroen Roovers
2013-05-22 15:36 ` Jeroen Roovers
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=20130523234042.26eaac89@caribou.gateway.2wire.net \
--to=dirtyepic@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