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. One of the features I had always planned to add to 'wx backup' was proper support for named backups. I occasionally rename a numbered backup (eg rename backup 24 to codereview-start), if you know the names 'wx restore' will happily restore them for you anyway. So I think we need something that does the full equivalent for mercurial that 'wx backup' does today for teamware. For me that means storing both committed and uncommitted file changes. Also a HUGE +1 to what Dan Price said about wx backup being used because we don't backup build machines. A few years ago I experimented with having Networker ignore object code, proto areas etc but even that still generated too much code. For me 'wx backup' isn't about disk failure so much as about finger/brain failure - it is really 'wx checkpoint' as well as backup. -- Darren J Moffat _______________________________________________ tools-discuss mailing list [email protected]
