From owner-freebsd-bugs Mon May 21 2:36:26 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1C79237B440; Mon, 21 May 2001 02:36:25 -0700 (PDT) (envelope-from roam@FreeBSD.org) Received: (from roam@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f4L9aNF78551; Mon, 21 May 2001 02:36:23 -0700 (PDT) (envelope-from roam) Date: Mon, 21 May 2001 02:36:23 -0700 (PDT) From: Message-Id: <200105210936.f4L9aNF78551@freefall.freebsd.org> To: roam@FreeBSD.org, freebsd-bugs@FreeBSD.org, ru@FreeBSD.org Subject: Re: misc/27491: buildworld failed due to kbdcontrol Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: buildworld failed due to kbdcontrol Responsible-Changed-From-To: freebsd-bugs->ru Responsible-Changed-By: roam Responsible-Changed-When: Mon May 21 02:33:00 PDT 2001 Responsible-Changed-Why: Actually, you're wrong - developers *are* aware of this problem. Ruslan Ermilov, who is currently working n kbdcontrol, has discussed it at length on the -current list (where this belongs), and on the cvs-all list (where all the commit messages and some followups go). As -current is a development branch of FreeBSD, problems with it do not really belong in PR's, but should rather be discussed on the appropriate lists. Still, thanks for taking the time to bring this problem to the developers' attention - although in this case it was already known, in other cases user feedback is important :) In the future, keep on giving feedback, but -current problems really belong on the freebsd-current list :) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27491 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message