> No, but just because someone wrote a nice feature, doesn't mean we should > commit it to the repository until it meets our style guidelines and we think > the changes are reasonable. A power model is great, but if it introduces a > 2x slowdown in simulation time irrespective if it's on or off then that > isn't going in the repository. So, what's the point of having a public tree if everything is pretty much "approved" by the main developers?
Is it just to commit bug-fixes? Is it OK to add new features? Basically, what are there going to be a set rules for pushing to the tree or at least a automatic regression test check on a push? Sounds like anything and everything should that is contributed should be through the patch/diff utility and then subjectively everyone tests and decides to put it in the main tree. To me, that sounds like you're asking for trouble if everyone has separate patches that need to be merged eventually. I dont know, but I trust that somebody has got the plan all figured out... -- ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
