What's the bigger picture here? Are you suggesting that we email all patches to the list for review before committing them? That sounds nice in principle but tedious in reality... though definitely valuable for things like Korey is discussing that are potentially widely visible changes.
Steve On Tue, Apr 1, 2008 at 8:55 AM, nathan binkert <[EMAIL PROTECTED]> wrote: > I just wanted to say that now that we're using mercurial, I'd like to > see us really using it well. I think we need to start having some > higher standards that are enforced across the board. > > I'm going to say that everyone that is an M5 developer *MUST* know and > use mercurial queues in their work. > http://www.selenic.com/mercurial/wiki/index.cgi/MqExtension > > Everyone also should start using this in conjunction with the > patchbomb extension: > http://www.selenic.com/mercurial/wiki/index.cgi/PatchbombExtension > > I'm going to pick on Korey just because he's actually working on > something that everyone is interested in. Korey, you should use mq to > manage your changes for the two things that you recently posted. (And > they should be two separate patches). You should then use "hg email" > to send your changes to the list. This method will both be faster and > be less error prone. > > I'm suggesting this because I want us to set a good example for others > given the imminent release of the repository. > > Everyone will get demonstrations of the e-mail extension from me very > soon as I plan to deluge you guys with my year of pending changesets. > > > Nate > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev >
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
