From owner-cvs-all  Sat Dec 12 17:12:44 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA21963
          for cvs-all-outgoing; Sat, 12 Dec 1998 17:12:44 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21958
          for <cvs-committers@FreeBSD.ORG>; Sat, 12 Dec 1998 17:12:42 -0800 (PST)
          (envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.1/8.9.1) id RAA13759;
	Sat, 12 Dec 1998 17:12:40 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 12 Dec 1998 17:12:40 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199812130112.RAA13759@apollo.backplane.com>
To: cvs-committers@FreeBSD.ORG
Subject: gnats database - what to do w/ 2.2.x bug reports?
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

    I've been browsing the bugs database and there are a whole bunch of
    2.2.x related bugs that I suspect are either fixed or -current or
    probably fixed in -current.

    I would like to categorize these bugs so I don't keep on going over
    them.  Can I move these bugs into a 'suspended' state or can we create
    a new 'depreciated' state or something to categorize these bugs ?  It
    would make management of gnats a bit easier.

						-Matt

    Matthew Dillon  Engineering, HiWay Technologies, Inc. & BEST Internet 
                    Communications & God knows what else.
    <dillon@backplane.com> (Please include original email in any response)    

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message