public inbox for insight-announce@sourceware.org
 help / color / mirror / Atom feed
From: Kip Warner <kip@thevertigo.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight-announce@sourceware.org, insight <insight@sourceware.org>
Subject: Re: RFC: Bug database cleaning
Date: Thu, 21 Feb 2008 01:48:00 -0000	[thread overview]
Message-ID: <1203557919.6994.1.camel@kip-laptop> (raw)
In-Reply-To: <47BCD137.3020806@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 914 bytes --]

On Wed, 2008-02-20 at 17:17 -0800, Keith Seitz wrote:
> Hi,
> 
> Most regulars probably know that I don't respond to bugs quite as 
> quickly as I should: I just seldom use the bug database -- largely 
> because as I respond to bugs, I seldom hear back from users.
> 
> As a result, the bug database is quite a bit larger than it should be. 
> So, I would like to close all bugs older than approximately one year. 
> That would affect any bug # less than 306.
> 
> Any one have any objections to this?

Provided those bugs on the tracker have been deemed invalid / closed /
resolved / patched / duplicate / whatever, then yes, of course.
Otherwise, you are losing a great deal of valuable information and the
fact that they just old doesn't really seem like reason enough to delete
them.

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-02-21  1:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  1:32 Keith Seitz
2008-02-21  1:48 ` Kip Warner [this message]
2008-02-21 15:31 ` terptom
2008-02-21 16:52   ` Keith Seitz

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=1203557919.6994.1.camel@kip-laptop \
    --to=kip@thevertigo.com \
    --cc=insight-announce@sourceware.org \
    --cc=insight@sourceware.org \
    --cc=keiths@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).