From owner-freebsd-bugs@FreeBSD.ORG Thu Dec 7 13:50:09 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07F1F16A412 for ; Thu, 7 Dec 2006 13:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DBFF43CAE for ; Thu, 7 Dec 2006 13:49:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kB7Do7bc048287 for ; Thu, 7 Dec 2006 13:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kB7Do7Ir048280; Thu, 7 Dec 2006 13:50:07 GMT (envelope-from gnats) Date: Thu, 7 Dec 2006 13:50:07 GMT Message-Id: <200612071350.kB7Do7Ir048280@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Gareth McCaughan Cc: Subject: Re: kern/100683: [syscons] [patch] syscons screen savers can eat up to 75% of CPU X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gareth McCaughan List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 13:50:09 -0000 The following reply was made to PR kern/100683; it has been noted by GNATS. From: Gareth McCaughan To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/100683: [syscons] [patch] syscons screen savers can eat up to 75% of CPU Date: Thu, 7 Dec 2006 13:49:42 +0000 (Apologies if I just submitted an empty followup; typo.) It's getting on for 6 months since this was submitted. It appears to be being entirely ignored. Is there anything I, as submitter and patch-writer, can do to help get it sorted? For instance, if the patch I supplied is considered unsatisfactory in some way then I can try to provide a better one. Or is the problem simply that the project doesn't have the resources to pay any attention to non-critical bugs? (Fair enough if so, I guess.)