Vladimir Marek wrote: >> I have some idea. 8^) wx backs up: > > :) > > >> 1. files in the active list including the SCCS s. and p. files (if the >> file is checked out). >> 2. The wx new list which is a wx state file that tracks newly created >> files in the workspace. >> 3. The wx renamed list (files that have been renamed in the workspace). >> 4. The wx sort_active state file (indicates user's preference in regards >> to wx keeping the active list sorted). >> 5. The wx *.NOT files which allow the user to record files which are >> exempt from certain wx putback checks like cstyle, etc... >> 6. The wx local_nametable file which is a subset of the local workspaces >> nametable containing the entries associated with the active, new and >> renamed lists. >> >> While generating this list I realize that wx should also backup the >> wx/backup_dir file but I haven't seen too many complaints about this so >> I'm not going to worry about it. > > Ok. Let's return to the original post starting this thread. Mercurial > does not support wx backup/restore functionality. If it is planned to be > ported, no idea, but would be really nice. > > If cdm is going to be serious wx replacement, it should be implemented > there, IMO.
Yes, and as Rich mentioned already - we filed an RFE for it yesterday. cheers, steve -- stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development _______________________________________________ tools-discuss mailing list [email protected]
