From owner-freebsd-current Thu Feb 5 11:18:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10836 for current-outgoing; Thu, 5 Feb 1998 11:18:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10811 for ; Thu, 5 Feb 1998 11:18:27 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA00727 for current@freebsd.org; Thu, 5 Feb 1998 14:18:23 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802051918.OAA00727@dyson.iquest.net> Subject: Comment about -current bug reports To: current@FreeBSD.ORG Date: Thu, 5 Feb 1998 14:18:23 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Please, whenever reporting a bug about -current, specify the date (and even time) of your last update to your source tree. When someone says that there is a problem with -current, since there is no time associated with the name "-current", I cannot tell if the problem is an old one and has been fixed or hasn't been fixed yet. So, if a bug report simply says "I am having this or that problem with -current", it might be ignored because of a lack of needed and critical info. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.