Vladimir Kotal <Vladimir.Kotal at Sun.COM> writes: > Vladimir Kotal wrote: >> Hi all, >> >> lib/python/onbld/Scm/Backup.py does backup of .hg/hgrc which contains >> the path to parent. This breaks things if backup repository uses local >> clone and restore repository another local clone (model where sparse >> builds are done locally and nightlies on build machine e.g. in another >> geo are pretty common AFAIK). >> >> Does this sound like a bug to anyone ? > > wx_backup() in wx previously only provided backup of active list > metadata plus the actual data files and it ignored Codemgr_wsdata > directory contents (which contains 'parent' file with path to parent > workspace) so it's definitely a change in the behavior. > > CR 6738179 filed.
Right, my view was that you may have settings in the workspace .hgrc other than the parent, and that are worthy of backing up, I still hold that view. I'm not entirely sure why a restore restoring *all* those settings is problematic, either. If you're restoring and your clone has moved, reparent the workspace after you restore. I'd imagine, given the above, that you're using backup/restore to move changes between machines? If so, why would you do that rather than pushing or pulling to the other machine? -- Rich
