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; 28 Aug 2004 02:22:22 +0000
>From [EMAIL PROTECTED] Fri Aug 27 19:22:22 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kmccarty.student.princeton.edu (arcturus.localdomain)
[140.180.135.112]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C0srG-0005mB-00; Fri, 27 Aug 2004 19:22:22 -0700
Received: from kmccarty by arcturus.localdomain with local (Exim 3.36 #1
(Debian))
id 1C0sql-0007Xi-00
for <[EMAIL PROTECTED]>; Fri, 27 Aug 2004 22:21:51 -0400
To: [EMAIL PROTECTED]
Subject: oops: Incorrect use of "it's" in package description
Reply-To: Kevin B. McCarty <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
From: "Kevin B. McCarty" <[EMAIL PROTECTED]>
Date: Fri, 27 Aug 2004 22:21:51 -0400
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:
Package: oops
Version: 1.5.23.cvs-2
Severity: minor
Hello,
The package oops uses the contraction "it's" in the
Description field of its control file in what appears to be an
incorrect way. Recall that "it's" is a contraction for "it is" or
"it has", and any other use (for instance, as a possessive) is not
grammatically correct English. Hypothetical examples:
- XMMS is cool. It's one of the best ... [correct, "It is"]
- XMMS is cool. It's been rated highly ... [correct, "It has"]
- XMMS is cool. It's features include ... [wrong]
- XMMS is cool. Its features include ... [correct, possessive]
Using "it's" and "its" correctly is in your best interest, since
incorrect usage may cause someone browsing the package descriptions to
have a bad first impression of that package.
Please note that this is a mass bug filing; it was discussed on
debian-devel in the thread starting here:
http://lists.debian.org/debian-devel/2004/08/msg01626.html
If you need to contact me, please respect the Reply-To header or use
my email address (in the .sig), as this bug report was sent from a
machine with no capability to receive email.
Best regards,
--
Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department
WWW: http://www.princeton.edu/~kmccarty/ Princeton University
GPG public key ID: 4F83C751 Princeton, NJ 08544
---------------------------------------
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]
