Ok. Stepping back a little ways.
We need a formula for doing incremental development that will allow us to
make headway while not seeing the entire picture all at once. The scope
is just too large.
The usual pattern is for someone to do implement the code in the order
and the fashion that seems obvious and then to reimplement it with a
history that is aids code reviews, and makes it obvious what is
happening. The reimplementation results in the exact same code but
the steps to get there are different.
We can either do that as individuals or as a group. But that
is the only pattern I know of that allows us to be comprehensive
when we merge and fall short during development.
Eric
-
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]
