Stephen Clark wrote:
So if someone in "the community" really wanted to help Intel why don't
they take the
code Intel posts to the ipw3945 ml and put it into where ever it is
really supposed to go?
Instead of whining how Intel doesn't do it right.
Unscalable.
People in the past sometimes asked Linus, "why didn't you go to $foo.com
website and download the patches? they work for me!" Same reason:
it's unscalable.
For each step in the maintainership pyramid of trust, the number of
people at that level decreases from the previous step. Patches trickle
-up- from sub-maintainers to maintainers to Andrew and finally Linus.
Thus, it is unreasonable for a kernel maintainer to poll $N mailing
lists, coalesce the opinion, grok the code, make sure the code is at a
point where it is OK to push upstream, and then push. That's a
one-to-many operation.
In contrast, a WORKING example of kernel development is a many-to-one
process. Driver maintainers send patches to subsystem maintainers.
Subsystem maintainers send patches to higher-level subsystem
maintainers. High-level subsystem maintainers send patches to Andrew
and Linus.
That's scalable.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
