Your message dated Thu, 26 Jan 2006 15:25:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in 1.5.23.cvs-3
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 maintonly) by bugs.debian.org; 19 Oct 2004 06:11:58 +0000
>From [EMAIL PROTECTED] Mon Oct 18 23:11:58 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dialin-80159.ewetel.net (rain.florz.dyndns.org) [212.6.80.159]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CJnDt-0006O5-00; Mon, 18 Oct 2004 23:11:58 -0700
Received: from florz.florz.dyndns.org ([192.168.0.121])
by rain.florz.dyndns.org with esmtp (Exim 3.35 #1 (Debian))
id 1CJnDg-00055t-00
for <[EMAIL PROTECTED]>; Tue, 19 Oct 2004 08:11:40 +0200
Received: from florz by florz.florz.dyndns.org with local (Exim 3.35 #1
(Debian))
id 1CJnDf-0002j4-00
for <[EMAIL PROTECTED]>; Tue, 19 Oct 2004 08:11:39 +0200
Date: Tue, 19 Oct 2004 08:11:39 +0200
From: Florian Zumbiehl <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: package description typo(s) and the like
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: oops
Version: 1.5.23.cvs-2
Severity: minor
I searched through the Packages file a bit for typos and the like - below
you find a diff of this package's description (a) showing what I think is
wrong and (b) how I suggest it to be corrected.
Description: HTTP caching proxy server written for performance
- A lightweight but powerful proxy cache. It's main features are:
+ A lightweight but powerful proxy cache. Its main features are:
* HTTP/1.1 (without persistent connections yet) and FTP
* Fast start. It is ready to serve requests immediately after start.
* On-disk storages are checked in background, while serving requests
directly from network
* Clean reconfiguration on SIGHUP - no broken sessions, new settings
applied to new connections
* Easy-to-read/understand config file and ACLs
* Bandwidth control
* Modular structure. Several module types exist: logging, access, output,
error reporting, URL filtering, ...
* Objects are stored in large files: no file per object scheme.
* These large files can be raw devices (like /dev/hda)
---------------------------------------
Received: (at 268533-done) by bugs.debian.org; 26 Jan 2006 14:25:25 +0000
>From [EMAIL PROTECTED] Thu Jan 26 06:25:25 2006
Return-path: <[EMAIL PROTECTED]>
Received: from tauware.de
([213.239.237.3] helo=freiburg.chummer.net ident=Debian-exim)
by spohr.debian.org with esmtp (Exim 4.50)
id 1F283x-0004DA-7B
for [EMAIL PROTECTED]; Thu, 26 Jan 2006 06:25:25 -0800
Received: from siretart by freiburg.chummer.net with local (Exim 4.50)
id 1F283w-0001jk-6P
for [EMAIL PROTECTED]; Thu, 26 Jan 2006 15:25:24 +0100
Date: Thu, 26 Jan 2006 15:25:24 +0100
To: [EMAIL PROTECTED]
Subject: fixed in 1.5.23.cvs-3
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
From: Reinhard Tartler <[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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Version: 1.5.23.cvs-3
I forgot to mention this bug in the changelog
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
