On Sun, 2006-07-23 at 01:20 -0600, Hans Reiser wrote:
> Jeff, I think that a large part of what is going on is that any patch
> that can be read in 15 minutes gets reviewed immediately, and any patch
> that is worked on for 5 years and then takes a week to read gets
> neglected. This is true even if line for line the 1 week to read patch
> is more valuable. What is more is that people know this is
> irrational, but aren't able to cure it in themselves. Even I have a
> problem of paying too much attention to endless 5 minute emails when I
> know I should instead, say, read the compression plugin from beginning
> to end.
>
> There is nothing about small patches that makes them better code. There
> is no reason we should favor them, if the developers are willing to work
> on something for 5 years to escape a local optimum, that is often the
> RIGHT thing to do.
>
> It is importand that we embrace our diversity, and be happy for the
> strength it gives us. Some of us are good at small patches that evolve,
> and some are good at escaping local optimums. We all have value, both
> trees and grass have their place in the world.
>
Which is summed up quite well by:
http://en.wikipedia.org/wiki/Color_of_the_bikeshed
It seem to be a well know tendency for people to want to
be involved in some way, thus keeping to much of the development
cycle internal tends to generate friction.
-Russell Cattelan
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
