> As for the bugs getting fixed, one of the main problems with EVMS merge
> now is that it (as any merge) shifts part of that very burden from EVMS
> maintainers to other developers *and* *it* *shifts* *too* *much*.
> That's what "ready to be merged" boils down to. It's a question of how
> many problems will be inflicted by the merge upon current and future
> development - over all kernel. AFAICS in its current state EVMS is not
> ready. And yes, it means that EVMS maintainers get to play catch up for
> a while.
We don't want to shift the burden of EVMS onto
other developers. We are willing to play catch up
for a while, however the feature-freeze date is
looming.
> Nobody refuses to help them, BTW.
Can you identify areas you feel need special
attention?
Mark
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/