From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Wed, 18 Jan 2006 19:10:32 -0500

> Its just plain inefficient.

I think part of this has to do with Intel's internal legal
policies for public code release.  It's time consuming and
highly encourages the engineers to batch code releases so
that they minimize the times they have to go through the
legal department.

It's pretty stupid and counter productive, and in this case here
resulted in Intel's engineering process looking rather poor.  This
e1000 incident is one of the worst vendor driver maintainence bombs
I've seen in my 10+ years of doing Linux kernel work.

If they don't fix their process and policies for external code
releases, this "massive code drop" problem will never go away.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to