> I meant "who's stopping you from committing the driver", not "who's
> stopping you from committing the driver to 2.2". I too think 2.2
> should be left to die in peace.
Well, before it is committed I would like to see one of you FreeBSD
wizards to check it over for a half hour first. My experience with
FreeBSD is one of rock-solid performance. I would hate to upset that
impression for somebody else with this particular chunk of code. I
wrote this driver to the best of my abilities, and I think it is good,
but I don't spend every weekend with the FreeBSD source code like some
of you guys do.
I can say with 100% certainty that my driver works much faster, more
reliably, and with more features than the current gp driver
distributed with FreeBSD for _me_. This will probably be true for
most other people as well. However, that doesn't mean that this code
is the end all and shouldn't be committed without being checked over
by one of you FreeBSD-god types. Maybe this is just my own anxiety
over my FreeBSD-contributer virgin status, but it seems wise.
Should I send it in with this "send-pr" command myself, or should I
let one of you guys do it?
John
--
John Galbraith email: j...@ece.arizona.edu
University of Arizona, home phone: (520) 327-6074
Los Alamos National Laboratory work phone: (520) 626-6277
home page: www.ece.arizona.edu:/~john
"As had been true historically, Gates' concern was not making great
products, but keeping the world locked into using his products."
--- Wendy Goldman Rohm, The Microsoft File
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
