On Jun 7, 2008, at 6:02 PM, nathan binkert wrote: >> Another reason to have separate repos instead of just tagging if >> we're >> going to do stuff at this rate is that each retagging generates a new >> changeset. Pulling from a repo named x to a repo named y doesn't. > I'm not sure if this bothers me. I guess it makes the history really > verbose. If stable is automatically done by the regression suite, > then I think it's fine to have a separate repo. What do people think > about the idea of automatic push of stable if a full regression > passes? (We can of course still tag at some longer interval when > important milestones have been reached.) I don't think it's too much to ask for someone to manually run update- stable.sh every few weeks, especially if there is an automated script that is reminding them that there are candidate revisions for moving to stable available.
Ali _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
