On Tue, Jan 08, 2013 at 12:42:19PM +0000, John Long wrote: > On Tue, Jan 08, 2013 at 01:31:18PM +0100, Stephan Beal wrote: > > On Tue, Jan 8, 2013 at 1:22 PM, John Long <codeb...@inbox.lv> wrote: > > > > > I just finished deleting a few dozen repos since I moved a bunch of source > > > code to another machine and fossil refused to like it. After that I found > > > a > > > discussion on the mailing lists about test-move-repository. Not a big deal > > > since this was all test stuff but I would like to know what the official > > > approved way is to let fossil know a repository has been moved. > > > > > > For example: > > > > > > old repo was in /home/user/code/project > > > > > > copied the project directory including the repo to > > > /newmachine/differentuser/programs/newplace > > > > > > > The easiest way, IMO, is: > > > > fossil close > > move repo file > > fossil open --keep /path/to/new/repo > > > > The --keep option keeps fossil from overwriting any changes you made > > between moving and opening the repo. > > Closing the repo isn't always going to be an option. For example when you > have to restore from a backup or are wiping a system to install a new > system you may not be able to find all the repos and close them. I am > working from backups in my example. fossil wouldn't let me open the repo. > > I haven't thought it through from a file integrity point of view but I'm > looking for a way to do this given the repo is open and is in a new > location. >
Also, by closing the repo, you will loose your stash and latest undo's (if you have some) -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
