On 3/29/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
>       <particle>      and i'm not interested in testing every revision,
>       when so many might be coding standards

Why are people even checking things in that fail coding standards?

because not all coding standard tests are run with 'make test'. some
tests were still under development, or too noisy, or took too long.
this means that running
 make test
and running
 prove t/codingstd

will give you *very* different results. the correctness and
performance problems with coding standard tests have largely been
solved, and i'm now in favor of enabling all these tests during make
test. this will require a large number of commits up front to fix the
current list of failures, but would prevent developers from committing
code that's not up to snuff.

~jerry

Reply via email to