From owner-freebsd-current@FreeBSD.ORG Fri Jun 4 11:23:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9947316A4CE for ; Fri, 4 Jun 2004 11:23:45 -0700 (PDT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24D5E43D1F for ; Fri, 4 Jun 2004 11:23:45 -0700 (PDT) (envelope-from conrads@cox.net) Received: from ip68-11-70-23.no.no.cox.net ([68.11.70.23]) by lakermmtao08.cox.netESMTP <20040604182312.WBXA5121.lakermmtao08.cox.net@ip68-11-70-23.no.no.cox.net>; Fri, 4 Jun 2004 14:23:12 -0400 Received: from ip68-11-70-23.no.no.cox.net (localhost.no.no.cox.net [127.0.0.1])i54INCA7005781; Fri, 4 Jun 2004 13:23:12 -0500 (CDT) (envelope-from conrads@ip68-11-70-23.no.no.cox.net) Received: (from conrads@localhost)i54IN69m005780; Fri, 4 Jun 2004 13:23:07 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040604165742.GP92188@cnd.mcgill.ca> Date: Fri, 04 Jun 2004 13:23:06 -0500 (CDT) From: Conrad Sabatier To: Mathew Kanner cc: freebsd-current@freebsd.org Subject: Re: What happened to src/sys/dev/sound/midi ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 18:23:45 -0000 On 04-Jun-2004 Mathew Kanner wrote: > > In regards to MIDI, I've been posting links to patches for > about a year now. I've had relatively little feedback. I'm not sure if > the current patches that are posted will compile after some changes to > infrastructure. Yes, and I'm one of those who really would have liked to have offered more in the way of feedback as you were developing this new code, but I really don't like patching existing kernel sources with new, untested, uncommitted code. It's just something I'm generally leery about doing. I was also doubtful that the patches would even apply cleanly from one build to the next, as I'm running CURRENT and updating quite frequently. Sorry for not providing more support for your work, which I am *definitely* interested in. -- Conrad Sabatier - "In Unix veritas"