From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Quantity of open bugs
Date: Thu, 10 Mar 2011 22:46:37 -0600 [thread overview]
Message-ID: <20110310224637.149e16da@gentoo.org> (raw)
In-Reply-To: 20110310202510.45627780@athlong2.kevquinn.com
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
On Thu, 10 Mar 2011 20:25:10 +0000
"Kevin F. Quinn" <ml@kevquinn.com> wrote:
> I would guess these old untouched bugs aren't actually going to be
> touched, ever - a lot simply won't be relevant any more for one reason
> or another. All they're doing is cluttering up bugzilla.
I never understand this argument. How does an open bug "clutter" up bugzilla
any more than a closed bug?
It's pretty simple. If a bug isn't fixed, it should be open. Automatically
closing them doesn't make things "better", it just generates shitloads of
useless mail.
--
fonts, gcc-porting, it makes no sense how it makes no sense
toolchain, wxwidgets but i'll take it free anytime
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-11 4:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110307130425.3C1ED1C042@pigeon.gentoo.org>
2011-03-10 20:25 ` [gentoo-dev] Quantity of open bugs Kevin F. Quinn
2011-03-10 21:03 ` [gentoo-dev] " Duncan
2011-03-10 21:33 ` [gentoo-dev] " Chris Richards
2011-03-11 4:46 ` Ryan Hill [this message]
2011-03-11 8:07 ` Alec Warner
2011-03-11 8:25 ` George Prowse
2011-03-11 14:13 ` Thomas Kahle
2011-03-12 14:45 ` [gentoo-dev] " Diego Elio Pettenò
2011-03-12 17:09 ` Donnie Berkholz
2011-03-12 17:16 ` [gentoo-dev] " Diego Elio Pettenò
2011-03-16 4:17 ` [gentoo-dev] " Jeroen Roovers
2011-03-16 9:46 ` [gentoo-dev] " Tomáš Chvátal
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=20110310224637.149e16da@gentoo.org \
--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