From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: changes to tested bugzilla keyword proposal
Date: Sun, 3 Feb 2013 01:41:00 -0600 [thread overview]
Message-ID: <20130203014100.390d894a@caribou> (raw)
In-Reply-To: CAGfcS_nt2DXzK0hD5YDus4OL1qs5j5heWKqqCGk02MLZP1qV-A@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On Fri, 1 Feb 2013 06:15:32 -0500
Rich Freeman <rich0@gentoo.org> wrote:
> On Fri, Feb 1, 2013 at 12:37 AM, Ryan Hill <dirtyepic@gentoo.org> wrote:
> >>
> >> If we added a "Keyword/Stable Request" component to the "Gentoo Linux"
> >> product we could also have it dependent on that, so only bugs in that
> >> component would display the flags.
>
> You'd need to include security bugs as well at the very least as they
> almost always include keyword changes.
Good catch.
> Are there any issues with changing the product/component on existing
> bugs? I could see things turn into keyword requests which didn't
> start out as such.
The message I quoted was from 2008. We've added a Keywording and
Stabilization component since then so we're halfway there already.
--
gcc-porting
toolchain, wxwidgets learn a language baby, it's that kind of place
@ gentoo.org where low card is hunger and high card is taste
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-02-03 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 16:17 [gentoo-dev] changes to tested bugzilla keyword proposal Vicente Olivert Riera
2013-01-09 16:39 ` Markos Chandras
2013-01-09 17:02 ` Jeroen Roovers
2013-01-09 19:49 ` Rich Freeman
2013-02-01 5:37 ` [gentoo-dev] " Ryan Hill
2013-02-01 11:15 ` Rich Freeman
2013-02-03 7:41 ` Ryan Hill [this message]
2013-02-03 8:21 ` Ryan Hill
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=20130203014100.390d894a@caribou \
--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