public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirkjan Ochtman <djc@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Last time touched bugs by year
Date: Fri, 15 Feb 2013 13:35:14 +0100	[thread overview]
Message-ID: <CAKmKYaCRmCxuzkL6qZky=0XqTR7icO8A-eB5CgqQGDdfig4Q9Q@mail.gmail.com> (raw)
In-Reply-To: <2721009.MOcim2sagC@arcarius>

On Thu, Feb 14, 2013 at 7:19 PM, Tomáš Chvátal <tomas.chvatal@gmail.com> wrote:
> I think it is lame we have bugs last touched in 2k5 :-P

Yeah, very useful. I went through most of the Python bugs and cleaned some up.

It looks like there's a *lot* of maintainer-wanted bugs that are very
old. I wonder if we can script cleaning those up; check how many CC
addresses, see if the upstream HOMEPAGE is still up, that kind of
things.

Cheers,

Dirkjan


  parent reply	other threads:[~2013-02-15 12:35 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 [this message]
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
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='CAKmKYaCRmCxuzkL6qZky=0XqTR7icO8A-eB5CgqQGDdfig4Q9Q@mail.gmail.com' \
    --to=djc@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