public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Handling of keywording bugs with only one arch
Date: Sat, 13 Mar 2010 19:21:52 +0200	[thread overview]
Message-ID: <4B9BC9B0.1020907@gentoo.org> (raw)
In-Reply-To: <4B9BC65D.9000504@gentoo.org>

On 03/13/2010 07:07 PM, Petteri Räty wrote:
> When a bug is marked as fixed it doesn't show up in searches developers
> use so it's a matter of who reads the email and acts upon it. I don't
> see why maintainers would be any more likely to act than an arch team
> comprised of multiple people in the case of bigger arches. Let's not
> forget that users are really supposed to open new bugs instead of
> commenting on the resolved ones although I know there are users out
> there who rather comment on a two year old only distantly related bug
> than open a new one.

I would love to see a bugzilla feature that would entirely disable
commenting on closed bugs like on archlinux's bugtracking system[1]

[1] http://www.mail-archive.com/arch-general@archlinux.org/msg11996.html

That might possibly need "Request reopen" button of somesort, or we
could just always require people to open new bugs

Often people just wish to argue about the closing status, after the bug
has been resolved...



  reply	other threads:[~2010-03-13 17:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 19:18 [gentoo-dev] Handling of keywording bugs with only one arch Petteri Räty
2010-03-12 19:39 ` "Paweł Hajdan, Jr."
2010-03-12 19:55   ` Petteri Räty
2010-03-12 19:54 ` Samuli Suominen
2010-03-12 20:11 ` Jeremy Olexa
2010-03-12 21:47   ` William Hubbs
2010-03-12 22:58     ` Jorge Manuel B. S. Vicetto
2010-03-13 11:08     ` Markos Chandras
2010-03-13 17:09     ` Petteri Räty
2010-03-13 17:07   ` Petteri Räty
2010-03-13 17:21     ` Samuli Suominen [this message]
2010-03-13 17:27       ` Petteri Räty
2010-03-13 22:43       ` [gentoo-dev] " Duncan
2010-03-14  8:56     ` Ryan Hill
2010-03-14  9:21       ` Petteri Räty
2010-03-14 23:41         ` Ryan Hill
2010-03-12 23:03 ` Ryan Hill
2010-03-12 23:17   ` Matti Bickel
2010-03-14 16:38 ` [gentoo-dev] " Thomas Sachau
2010-03-27 14:26 ` Petteri Räty
2010-03-27 14:51   ` Alex Alexander
2010-03-27 15:07     ` Petteri Räty
2010-04-01 20:28       ` Jeroen Roovers
2010-04-04  9:38         ` Petteri Räty
2010-03-27 16:45   ` [gentoo-dev] " Torsten Veller
2010-03-27 16:51     ` Alec Warner
2010-03-27 17:20       ` Matti Bickel
2010-04-10 22:38   ` Ryan Hill
2010-04-10 22:41     ` Petteri Räty
2010-04-10 23:12       ` 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=4B9BC9B0.1020907@gentoo.org \
    --to=ssuominen@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