svn commit: r184610 - in head: lib/libusb20 share/man/man4 sys/conf sys/dev/sound/pcm sys/dev/usb2 sys/dev/usb2/bluetooth sys/dev/usb2/controller sys/dev/usb2/core sys/dev/usb2/ethernet sys/dev/usb...

[M. Warner Losh]

In message: <49134F1C.2000102 at FreeBSD.org>
            "Bruce M. Simpson" <bms at freebsd.org> writes:
: M. Warner Losh wrote:
: > ...
: > : > So the question is, why was this code imported at all?
: > : 
: > : Seconded, especially since it says the code was reviewed by you Warner in
: > : the commit log.
: >
: > Unfortunately, most of my reviews were ignored, as were those of a
: > great many other people.  There's lots of pressure for this code from
: > the user community.  It is an experiment, one that may well ultimately
: > fail.
: 
: Or ultimately succeed. I have every confidence in Alfred's ability to 
: see things through.

Alfred doesn't matter so much here.  Not to minimize his work to date
in coordination for usb2, but it won't succeed or fail based on him
alone.  The success or failure of this will be how well hps can cope
with the code being shared.  How well the FreeBSD developers adapt the
code to be closer to FreeBSD standard in a number of areas.  How well
people are able to fix the flaws that grew into this code base as it
developed in isolation.

: It is better that this is happening now, after the SVN import, therefore 
: the change cost may not be so great as it may have been with CVS.

This is true.

: One of the long-standing problems with FreeBSD is that we have been too 
: conservative in what we've allowed into the code base. There are sound 
: and compelling reasons why we have such rules, however, it's worth 
: remembering that competition has been able to get a foothold in various 
: key areas that could have been expanded into.

I'm not so sure I agree with this.  The problems with the usb import
was social, not technical.

Warner