From owner-freebsd-current Wed Jul 1 12:50:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09718 for freebsd-current-outgoing; Wed, 1 Jul 1998 12:50:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09711 for ; Wed, 1 Jul 1998 12:50:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00716; Wed, 1 Jul 1998 21:47:44 +0200 (CEST) To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: bin/7059 (fwd) In-reply-to: Your message of "Wed, 01 Jul 1998 13:01:49 EDT." <199807011701.NAA08352@rtfm.ziplink.net> Date: Wed, 01 Jul 1998 21:47:44 +0200 Message-ID: <714.899322464@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807011701.NAA08352@rtfm.ziplink.net>, Mikhail Teterin writes: >Is this a new policy for a PR database? This is only one of the >PRs I submitted, which are "suspended". It looks suspiciously like >dust that goes under carpet... I understand, there is lack of >time*people to fix them, but why suspend? It is a relatively new policy, I try to get through the database. Things that have merit, but are unlikely to happen unless somebody takes a fancy in them are moved to suspended, leaving "open" to mean "still to be decided on" more or less. suspended was not used for anything else, and does sadly enough reflect will on the progress on many of these good and well deserving topics. Including patches improves your situation a lot of course, but still no guarantees can be given. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message