All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Stephen.Clark@seclark.us
Cc: David Miller <davem@davemloft.net>,
	jketreno@linux.intel.com, axjslack@bluebottle.com,
	linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] Request for help...
Date: Tue, 24 Jul 2007 21:40:04 -0400	[thread overview]
Message-ID: <46A6A9F4.1040603@garzik.org> (raw)
In-Reply-To: <46A69CA1.5020706@seclark.us>

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



  parent reply	other threads:[~2007-07-25  1:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-24 15:02 Request for help Axj
2007-07-24 16:12 ` John W. Linville
2007-07-24 18:29   ` [ipw3945-devel] " Stephen Clark
2007-07-24 20:30     ` John W. Linville
2007-07-24 21:13       ` Jeff Garzik
2007-07-25  1:15         ` James Ketrenos
2007-07-25  0:03           ` Jeff Garzik
2007-07-25  0:30             ` Stephen Clark
2007-07-25  0:35               ` David Miller
2007-07-25  0:43                 ` Stephen Clark
2007-07-25  0:46                   ` David Miller
2007-07-25  1:05                     ` Stephen Clark
2007-07-25  1:18                       ` David Miller
2007-07-25  1:23                       ` Jeff Garzik
2007-07-25  1:29                         ` Stephen Clark
2007-07-25  1:40                     ` Jeff Garzik
2007-07-25  1:40                   ` Jeff Garzik [this message]
2007-07-25  0:45               ` Maurizio Monge
2007-07-25  1:35               ` Jeff Garzik
2007-07-25  8:01             ` James Ketrenos
2007-07-25 14:50               ` John W. Linville
2007-07-27 12:36               ` Jeff Garzik
2007-07-25 14:46             ` John W. Linville
2007-07-25 15:19               ` Jeff Garzik
2007-07-25  9:32 ` Zhu Yi
2007-07-26 15:10   ` Axj
2007-07-26 16:22     ` Pavel Roskin
2007-07-27  6:34       ` Axj
2007-07-27  7:44         ` Zhu Yi
2007-07-27  8:48           ` Axj
     [not found]           ` <200707270848.l6R8mqkh004526@mi1.bluebottle.com>
2007-07-27  8:56             ` Zhu Yi
2007-07-27  9:10               ` Axj
2007-07-30  0:58                 ` Zhu Yi
2007-08-01  6:40                   ` Axj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46A6A9F4.1040603@garzik.org \
    --to=jeff@garzik.org \
    --cc=Stephen.Clark@seclark.us \
    --cc=axjslack@bluebottle.com \
    --cc=davem@davemloft.net \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=jketreno@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.