On Jan 30, 2008 2:50 AM, Steve Borho <[EMAIL PROTECTED]> wrote: > > > On Wed, 2008-01-30 at 01:46 +0000, TK Soh wrote: > > On Jan 29, 2008 11:02 PM, Peer Sommerlund <[EMAIL PROTECTED]> wrote: > > > People often mention mercurial queues as a nice tool for local work. Since > > > gquilt works with Mercurial, it could make sense to integrate it into thg. > > > > > > However, I don't think gquilt is sufficiently integrated with Mercurial > > > workflows. One step towards integration is to identify valuable use cases: > > > > > > On the mercurial mail list some persons indicate that they use mq for > > > temporary work, and want to share the patches between machines. This is > > > easier if you use qinit -c and share the mq repository. This could > > > probably > > > be made easier with some specific dialogs, bult upon the "Syncronize" > > > concept. > > > > > > When I hack away, I often mix new features, bug fixes, and local > > > environment > > > adaption. This can be supported with guards, but there may be even better > > > ways to support this. Maybe branches on the mq repo. > > > > > > How do you use mq? > > > > I almost never use mq myself. Though I acknowledge the importance of > > mq within the Mercurial community, so we will definitely want to have > > the support for mq in TortoiseHg. > > > > It a matter of when and how. > > I would like to add mq support (via gquilt or other) in the 0.4 or 0.5 > time-frame. I think in 0.4 we should try to improve support for named > branches.
We should add a roadmap to wiki similar to that of Mercurial. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
