From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last time touched bugs by year
Date: Fri, 21 Jun 2013 21:08:45 +0200 [thread overview]
Message-ID: <201306212108.45890.dilfridge@gentoo.org> (raw)
In-Reply-To: <CAG2jQ8iUU0heBg_BMryQ6qoTUuwVCP8eqXNtZd--h-JuL0-mAw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1295 bytes --]
Am Freitag, 21. Juni 2013, 14:50:29 schrieb Markos Chandras:
> On 21 June 2013 12:44, Tomáš Chvátal <tomas.chvatal@gmail.com> wrote:
> > 2013/6/21 Pacho Ramos <pacho@gentoo.org>
> >
> >> Could "maintainer-wanted" assigned bugs be filtered? Otherwise we see a
> >> ton of that kind of bugs that, I think, we already know can become
> >> really old ;)
> >>
> >> Thanks!
> >
> > You can do such yourself. Just clone the repo [1] and commit the updated
> > links.
> >
> > Also my plan was to list even m-w bugs, because even those suckers get
> > obsoleted often so we should close them.
> >
> > Cheers
> >
> > Tom
> >
> > [1]
> > http://git.overlays.gentoo.org/gitweb/?p=proj/qa-scripts.git;a=summary
>
> That is true. There is nothing special about there m-w bugs. They are
> still unresolved bugs, for many years. No need to treat
> them differently.
>
How can a m-w bug be resolved? Adding the package is unlikely to happen if
last request came years ago.
My suggestion would be (this is how I handled it in printing):
1) leave message on bug
"Is anyone still interested in this?"
2) if noone replies in 2 months, resolve as obsolete
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-06-21 19:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 18:19 [gentoo-dev] Last time touched bugs by year Tomáš Chvátal
2013-02-14 18:34 ` Markos Chandras
2013-02-14 19:26 ` Tomáš Chvátal
2013-02-15 9:43 ` Markos Chandras
2013-02-15 10:07 ` Tomáš Chvátal
2013-02-14 18:46 ` Agostino Sarubbo
2013-02-15 9:41 ` Tomáš Chvátal
2013-02-15 9:45 ` Alec Warner
2013-02-15 10:07 ` Tomáš Chvátal
2013-02-15 11:51 ` Gilles Dartiguelongue
2013-02-15 11:56 ` Tomáš Chvátal
2013-02-15 12:35 ` Dirkjan Ochtman
2013-06-21 11:28 ` Pacho Ramos
2013-06-21 11:44 ` Tomáš Chvátal
2013-06-21 12:50 ` Markos Chandras
2013-06-21 19:08 ` Andreas K. Huettel [this message]
2013-06-21 19:12 ` Michał Górny
2013-06-21 19:22 ` Sergey Popov
2013-06-21 19:27 ` Sergey Popov
2013-06-21 19:53 ` Alex Xu
2013-06-24 15:11 ` Ian Stakenvicius
2013-06-29 9:27 ` [gentoo-dev] " 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=201306212108.45890.dilfridge@gentoo.org \
--to=dilfridge@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