From owner-freebsd-ports@FreeBSD.ORG Mon May 10 11:14:46 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6042416A4CE for ; Mon, 10 May 2004 11:14:46 -0700 (PDT) Received: from albatross.mail.pas.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C4D843D53 for ; Mon, 10 May 2004 11:14:46 -0700 (PDT) (envelope-from mike@inbox.lv) Received: from pool0266.cvx35-bradley.dialup.earthlink.net ([216.244.13.11] helo=ringworm.mojavegreen.com) by albatross.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BNFIb-0002Hj-00 for freebsd-ports@freebsd.org; Mon, 10 May 2004 11:14:45 -0700 Received: by ringworm.mojavegreen.com (Postfix, from userid 1000) id 5DA3B86A7; Mon, 10 May 2004 11:07:26 -0700 (PDT) From: "Michael C. Shultz" Organization: Mojave Green Software co. To: freebsd-ports@freebsd.org Date: Mon, 10 May 2004 11:07:17 -0700 User-Agent: KMail/1.6.2 References: <200405101800.i4AI0cEJ094787@freefall.freebsd.org> In-Reply-To: <200405101800.i4AI0cEJ094787@freefall.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405101107.22106.ringworm@inbox.lv> Subject: Re: Current unassigned ports problem reports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 18:14:46 -0000 On Monday 10 May 2004 11:00 am, FreeBSD bugmaster wrote: > Current FreeBSD problem reports > > The following is a listing of current problems submitted by FreeBSD users. > These represent problem reports covering all versions including > experimental development code and obsolete releases. > > Bugs can be in one of several states: > > o - open > A problem report has been submitted, no sanity checking performed. > > a - analyzed > The problem is understood and a solution is being sought. > > f - feedback > Further work requires additional information from the > originator or the community - possibly confirmation of > the effectiveness of a proposed solution. > > p - patched > A patch has been committed, but some issues (MFC and / or > confirmation from originator) are still open. > > s - suspended > The problem is not being worked on, due to lack of information > or resources. This is a prime candidate > for somebody who is looking for a project to do. > If the problem cannot be solved at all, > it will be closed, rather than suspended. > > c - closed > A problem report is closed when any changes have been integrated, > documented, and tested -- or when fixing the problem is abandoned. > > Critical problems > > S Submitted Tracker Resp. Description Does this post mean you are looking for volunteers to fix some of these? If you are how does one go about volunteering? If not, why post this? -Mike