On Tue, Feb 26, 2008 at 9:56 AM, Richard Lowe <[EMAIL PROTECTED]> wrote: > > Trevor Watson <[EMAIL PROTECTED]> writes: > > > Stephen Hahn wrote: > >> * Shawn Walker <[EMAIL PROTECTED]> [2008-02-24 22:53]: > >>> As a result of the above process, do you tend to keep a working copy > >>> for each set of changes you are doing? > >> > >> I do--a separate child for each. Danek uses Mercurial Queues (mq) > >> sometimes, so he might have comments on how he handles multiple sets > >> of changes. > > > > For what it's worth, I do the same as Stephen - I can understand that > > model well as I have to do it for CVS repo's I use with other > > projects. > > > > I tend to do the "other" way Stephen described, a workspace per set of > changes with (sometimes numerous) intermediate commits, followed by a > recommit. > > (we (SCM) really should borrow some of this thread as documentation, > if this will be a common question, our assumption had been people > would continue with basically the same workflow they had anyway).
I think that that would be true for internal Sun folks; but for external contributors, like me, who haven't really used mercurial before, finding a good work-flow will be helpful. -- Shawn Walker, Software and Systems Analyst http://binarycrusader.blogspot.com/ "To err is human -- and to blame it on a computer is even more so." - Robert Orben _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
