From owner-freebsd-current@FreeBSD.ORG Tue Dec 23 20:17:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4EB31065674; Tue, 23 Dec 2008 20:17:02 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7C3A38FC19; Tue, 23 Dec 2008 20:17:01 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id E04A91A3C3A; Tue, 23 Dec 2008 12:17:01 -0800 (PST) Date: Tue, 23 Dec 2008 12:17:01 -0800 From: Alfred Perlstein To: Sam Leffler Message-ID: <20081223201701.GS18389@elvis.mu.org> References: <20081222214010.GA18389@elvis.mu.org> <86abanuhh5.fsf@ds4.des.no> <20081223144914.GO18389@elvis.mu.org> <863agevs8y.fsf@ds4.des.no> <20081223151942.GP18389@elvis.mu.org> <495125B2.1070806@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <495125B2.1070806@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: Dag-Erling Sm??rgrav , current@freebsd.org Subject: Re: HEADSUP usb2 (usb4bsd) to become default in 2 weeks. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2008 20:17:02 -0000 * Sam Leffler [081223 09:53] wrote: > Alfred Perlstein wrote: > >* Dag-Erling Sm??rgrav [081223 07:14] wrote: > > > >>Alfred Perlstein writes: > >> > >>>Dag-Erling Sm??rgrav writes: > >>> > >>>>Don't you think this should be discussed first? > >>>> > >>>If someone has a strong objection with some concrete issues > >>>I'm all ears. > >>> > >>You know very well that there are, and you also know very well that this > >>is too big a change to go in without discussion. > >> > > > >Perhaps you can list them for me, all I've seen so far is: > > > >1) Sam has code he doesn't want to port (Hans has stepped up to do so.) > >2) Another 1 or 2 developers have code that needs porting and we're > > in discussions with them about it. > >3) I think you were mad about whitespace or something, but like this > > case, you were not up for bringing specifics to the table. > > > >If you have something to add then please be more specific with your > >requirements. > > > > > > > As usual you've misconstrued my comment and ignored all the substantive > issues that have been brought up since the code was added to the tree. > The fact that you need people to list issues for you shows how out of > touch you are. It is pointless to argue issues with you yet again so I > will simply say that I have always been in favor of moving the usb code > base forward. In fact I strongly suggested you commit the new code _in > place_ of the existing code. As to my work I have said I'm not > interested in working w/ the new usb code so someone else will need to > bring in the missing functionality (same goes for all wireless > drivers). I believe that person has stepped up so this is not an issue > for me. Sam, I have an email address and since Hans and I are the points of contact for usb2 work I have seen little if any emails directed towards me in a constructive manner about the project from a few key detractors. There are a few shining examples of developer interaction with us, but unfortunately a bunch seem to be based on private emails, discussions on irc and other back channels that I'm just not privy to. Calling me "out of touch" for not being welded to the FreeBSD-rumor-mill is just unfair. So I implore you to take the high road and suggest that people take these issues to me directly when they come up, instead of blindsiding me when I try to take the next step with this project. In so far as telling me to bring it in place, perhaps I dream of black helicopters jumping fences instead of white sheep, but it really seemed that you were dead-set against the new stack to the point that I realized that putting the new stack over the old one, would suddenly have potentially huge backlash making the project a failure. You know that and I know that. Finally, since your concerns about your code are addressed, then why even bother responding? Let it go man. -- - Alfred Perlstein