On 2007-07-18 13:27, Darren J Moffat <[EMAIL PROTECTED]> wrote: >Giorgos Keramidas wrote: >>> The first of these I see fitting in reasonably well with hg bundle. >>> The second however what I really really want is to be able to revert >>> back to exactly the same point for source code I was in an hour, a day >>> or whatever ago. >> >> That's where MQ can prove handy. Uncommitted changes in a workspace can >> be saved with: >> # hg add foo >> # hg rename bar baz >> # edit some files >> hg qnew -f -m 'patch description' newpatch >> hg qcommit -m 'newpatch: save patch state' >> Then 'newpatch' appears as an already "pushed" patch, and it can be >> qpop'ed or qpush'ed at will. > > I don't think that is anything near as easy to understand as 'wx > backup' 'wx restore' is.
That's true :-/ > MQ just doesn't seem that intuative to me. Also remember that we have > to help those people who have been using teamware for a very long time > and requiring them to use MQ as well as base mercurial will hurt their > productivity for a non trivial amount of time. >> The tricky part is making sure that the ~/.hg/patches repository lives >> over NFS or some other place where it has more chance of surviving a >> complete and unrecoverable system crash. Symlinking .hg/patches to an >> NFS-shared location may work, but I haven't experimented with this yet. > > If it really is ~/.hg and not .hg in the workspace then that is > already equivalent to 'wx backup' since it uses ~/wx.backup/ Yes, that was meant to be a pointer to ~/patches instead of .hg/patches inside the workspace area. I did a short test with a symlinked patch queue which points from a local .hg/patches -> ~/safe-mq shortly after the original post, and it seems to work, so at least some amount of basic functionality is already available. It may be easier to do something like "wx backup" and "wx restore" with a custom extension though, if MQ is considered non-trivial and too counter-productive for every-day ON use. _______________________________________________ tools-discuss mailing list [email protected]
