Your message dated Wed, 21 Sep 2005 16:00:51 -0600
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Apr 2004 19:10:20 +0000
>From [EMAIL PROTECTED] Thu Apr 22 12:10:20 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail-relay-3.tiscali.it (mail-relay-3.tiscali.i) [212.123.84.93]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BGjaW-0000uv-00; Thu, 22 Apr 2004 12:10:20 -0700
Received: from tin.it (62.11.51.10) by mail-relay-3.tiscali.i (7.0.027)
id 4086A8B10000A1BE for [EMAIL PROTECTED]; Thu, 22 Apr 2004 21:09:49
+0200
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 22 Apr 2004 21:10:12 +0200
From: Gabriele Giorgetti <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 0.5 (X11/20040306)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: RFP: cpuspeedy -- A simple and easy to use program to control the
speed and the voltage of CPUs on the fly.
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.5 required=4.0 tests=BAYES_10,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
X-CrossAssassin-Score: 1
package: cpuspeedy
description: A simple and easy to use program to control the speed and
the voltage of CPUs on the fly.
http://cpuspeedy.sourceforge.net
---------------------------------------
Received: (at 245363-done) by bugs.debian.org; 21 Sep 2005 22:00:52 +0000
>From [EMAIL PROTECTED] Wed Sep 21 15:00:52 2005
Return-path: <[EMAIL PROTECTED]>
Received: from merkel.debian.org [192.25.206.16] (mail)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EICe4-0005Dh-00; Wed, 21 Sep 2005 15:00:52 -0700
Received: from damog by merkel.debian.org with local (Exim 3.36 1 (Debian))
id 1EICe3-0004UN-00; Wed, 21 Sep 2005 16:00:51 -0600
To: [EMAIL PROTECTED]
Subject: WNPP bug closing
Message-Id: <[EMAIL PROTECTED]>
From: David Moreno Garza <[EMAIL PROTECTED]>
Date: Wed, 21 Sep 2005 16:00:51 -0600
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Hello,
This is an automatic mail sent to close the RFP you have reported or
are involved with.
Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 450 days.
- It hasn't had any activity recently.
As this an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).
To re-open it, you simply have to mail [EMAIL PROTECTED]
with a body text like this:
reopen 245363
thanks bts
Further comments on the work done in the bug sent to
[EMAIL PROTECTED] would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.
This is the second massive wnpp closing that is being done. The next close
will be done on inactive RFPs older than 365 days and finally, an automatic
script will close, by default, *inactive* RFPs when they reach one year of
inactivity.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <[EMAIL PROTECTED]> Wed, 20 Sep 2005 17:06:42 -0500
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
