Why kernel development still uses email

> The question is can it/should it scale to a point where maintenance is "multi-threaded" with multiple maintainers for not even seeing all the patches for the subsystem they collectively own: a model already used elsewhere.

Don't get me wrong: in any review system you can *still* subscribe to everything and anything if you want to. Example: https://groups.google.com/a/chromium.org/forum/#!forum/ch...
(and of course pretty much every review system obeys the Law of Software Envelopment)

This is about the review system leaving a (fine-grained) *choice*; not forcing all users into an "all or nothing" decision on the premise that being notified of every single review event will make you smarter. Or... run away and ignore everything - so effectively a contributor selection system. A bit brutal but... desired and useful?