From owner-freebsd-doc@FreeBSD.ORG Mon Jul 7 16:34:33 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0077E37B401 for ; Mon, 7 Jul 2003 16:34:32 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43AC743FCB for ; Mon, 7 Jul 2003 16:34:32 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.9/8.12.3) with ESMTP id h67NY8ib009594; Mon, 7 Jul 2003 16:34:08 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id h67NY8OA009592; Mon, 7 Jul 2003 16:34:08 -0700 Date: Mon, 7 Jul 2003 16:34:08 -0700 From: Brooks Davis To: jonathan michaels Message-ID: <20030707233408.GA8258@Odin.AC.HMC.Edu> References: <200307071800.h67I0kDE031956@freefall.freebsd.org> <20030708091929.15647@caamora.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <20030708091929.15647@caamora.com.au> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: FreeBSD doc list Subject: Re: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jul 2003 23:34:33 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 08, 2003 at 09:19:29AM +1000, jonathan michaels wrote: > On Mon, Jul 07, 2003 at 11:00:46AM -0700, FreeBSD bugmaster wrote: >=20 > > Current FreeBSD problem reports >=20 > snipped ... >=20 > > Bugs can be in one of several states: > >=20 > > o - open > > A problem report has been submitted, no sanity checking performed. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ >=20 > in case the text gets mangled, the bit i'm seeking clarification for is > teh last bit of teh sentance "no santiy checking performed" and > specifically i do not understand teh meaning of "santiy checking" in > regards to teh submitted and peno problem report. It means that no human has verified the report makes any sense. It could be a valid bug, but it also could be spam, deranged rantings about a non-issue, or a user error reported as a bug. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/CgNuXY6L6fI4GtQRAiHtAKDKqO8Kq/8EspGHj02/XC7TrTOdzACeIvq3 ltEeN4pu5DuNE0UQJ10cHa0= =x9XV -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--