On 12/24/2015 6:42 AM, Jarkko Sakkinen wrote: > > Code is not rejected solely on its size as long as is broken up into > reasonable size and otherwise sane patches.
I'm still at the prime question. If we present a ~5 loc resource manager, can it be accepted, or will it be rejected as "too big"? ~~ We already went through the failing process with TPM 1.2. I had a 50 kloc TPM, and they wanted me to release it as <100 loc patches. 1 - How do you release an entirely new function as a patch. It's not patching anything? 2 - If you break it up, won't it be rejected because it doesn't work. It may not even compile? 3 - Breaking it up into small pieces that even compile can mean designing the code inefficiently. 4 - Or, are you saying that we code the entire RM, but just show it to you a function at a time? Can anyone review a bunch of functions without seeing how it fits together into a program? ~~ I can understand small "patches" to fix bugs, but not for new code. ------------------------------------------------------------------------------ _______________________________________________ tpmdd-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tpmdd-devel
