From owner-freebsd-bugs Sun May 12 09:41:15 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA29034 for bugs-outgoing; Sun, 12 May 1996 09:41:15 -0700 (PDT) Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA29025 for ; Sun, 12 May 1996 09:41:11 -0700 (PDT) Received: from palmer.demon.co.uk (localhost [127.0.0.1]) by palmer.demon.co.uk (sendmail/PALMER-1) with ESMTP id RAA07476 ; Sun, 12 May 1996 17:14:39 +0100 (BST) To: invalid opcode cc: freebsd-bugs@FreeBSD.ORG From: "Gary Palmer" Subject: Re: List of open Problem Reports In-reply-to: Your message of "Sun, 12 May 1996 02:07:17 PDT." Date: Sun, 12 May 1996 17:14:37 +0100 Message-ID: <7473.831917677@palmer.demon.co.uk> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk invalid opcode wrote in message ID : > I think all of the send-pr's that are -current specific, should be > removed, as by the very nature of -current, these are things most likely > being worked on or being fixed. Nope, -current users still need to send feedback to us about bugs in -current, and send-pr is the PROPER interface to use otherwise we have no way of tracking the bug & its fix. You must remember that people put FreeBSD-current under a lot more load in more situations than any of the developers can, so just because it's a bug in -current does NOT instantly mean that someone is working on fixing it as none of us (i.e. developers) may be able to find the bug without outside help... As for some of the other stuff that you flagged, perhaps you should read the PR before just instantly saying that we should close it. There is an interface available on the WWW pages for those without accounts on freefall ... And if you don't like using the web, I can dig out details of the mail interface too. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info