I think Gabe sums it up pretty nicely. Another way to phrase the same idea is that m5-dev is really for m5 *infrastructure* development.
I hadn't understood before why sometimes we get "user" questions on m5-dev, but Javier's explanation makes sense. Unlike most open-source projects, I think it's pretty rare that anyone using m5 for architecture research would be able to get anything useful done without hacking on the code; if m5 already implements your idea, then that's a sign that your research isn't very novel. I think most people realize that, but occasionally we get an email that's basically asking "where's the --isca-paper option?". Steve On Thu, Apr 23, 2009 at 1:15 AM, Gabe Black <gbl...@eecs.umich.edu> wrote: > No problem. It is a bit ambiguous, but my interpretation is that if > you're doing work that we'll be distributing with M5 to other people, > that goes on m5-dev. If you're doing development work but it's for your > own projects that goes on m5-users. I don't think we have an actual > official policy, but that's probably a good rule of thumb. > > Gabe > > Javier Jose wrote: > > > > Gabe: Cool, from now on I will post everything in m5-users. I posted > > here since it was concerning my on going development. It was a little > > confusing where to past what. >
_______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
