Steve Reinhardt wrote: > I went through and closed the tasks that were obviously obsolete from > my perspective. Nearly all of the rest look plausible to me, though > many are outside my area of familiarity (e.g., the x86- and > SPARC-specific ones). Perhaps the reality is that, as much as we'd > like to prune this list, there is a lot of work that could be done. > > We should move all the current MemorySystem tasks to a new category > (ClassicMemorySystem) and make a new RubyMemorySystem category (or > maybe just reuse MemorySystem for Ruby). I'm not sure we should get > rid of the current memory-system tasks, but as we move to Ruby maybe > they should all get lowered priorities or something. > > Maybe if everyone else goes through and cleans up the tasks they're > familiar with (looks like Korey has already started, thanks!) then we > won't need a phone call. > > We still have to figure out the "due in version" issue now that we > don't have version numbers (unless we re-introduce them as Nate > suggested). Maybe we should just get rid of that field? > > Steve > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev >
Sorry for not replying to this earlier. Every so often I think of flyspray for one reason or another and go wander through it, and I think the things that are mine are relatively cleaned up. I'll make another pass in the near future just to be sure. Gabe _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
