Re: "How to recognise different ETCH wishlists from quite a long way away" (revised)

To: debian-devel@lists.debian.org
Subject: Re: "How to recognise different ETCH wishlists from quite a long way away" (revised)
From: Olaf van der Spek <olafvdspek@gmail.com>
Date: Fri, 8 Jul 2005 18:22:52 +0200
Message-id: <[🔎] b2cc26e4050708092255776568@mail.gmail.com>
Reply-to: Olaf van der Spek <olafvdspek@gmail.com>
In-reply-to: <[🔎] Pine.LNX.4.62.0507081521350.13070@cantor.unex.es>
References: <[🔎] 20050708123148.GA9625@dat.etsit.upm.es> <[🔎] Pine.LNX.4.62.0507081521350.13070@cantor.unex.es>

On 7/8/05, Santiago Vila <sanvila@unex.es> wrote:
> Sure, old bugs may be the symptom that the maintainer is MIA, that the
> upstream maintainer is MIA, and similar things that we should of
> course track as well, but it does not mean that an old bug is "worse"
> in any way than a new bug (eveything else being the same).

What's the proper way to deal with maintainers that kinda 'ignore'
bugs (in whatever way)?

Reply to:

References:
- "How to recognise different ETCH wishlists from quite a long way away" (revised)
  - From: Javier Fernández-Sanguino Peña <jfs@computer.org>
- Re: "How to recognise different ETCH wishlists from quite a long way away" (revised)
  - From: Santiago Vila <sanvila@unex.es>

Prev by Date: Re: Question about kill(1)
Next by Date: Re: Drop the minor release number
Previous by thread: Re: "How to recognise different ETCH wishlists from quite a long way away" (revised)
Next by thread: Re: "How to recognise different ETCH wishlists from quite a long way away" (revised)
Index(es):
- Date
- Thread