On 2007-07-18 11:33, Darren J Moffat <[EMAIL PROTECTED]> wrote:
> One of the key features of wx backup for teamware is that it saves
> BOTH the checked in SCCS and the currently checked out versions of
> files. It also knows how to deal with renames to.
>
> I use wx backup for two different things.
>
> Sync with my parent:
> 1) wx delget ; wx backup ; bringover ; wx resolve ; wx edit
>
> Make a backup because I'm about to experiement with some changes and
> fully expect to have to revert back to the previous state, but I'm not
> ready to check anything in / commit yet.
>
> 2) wx backup ; continue editing.
>
> 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.
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.
_______________________________________________
tools-discuss mailing list
[email protected]
