OK, maybe I have a misunderstanding of the need for close. What is it used for? The claim by Stephan Beal that he hasn’t closed a repo more than 5 times over many years makes me wonder why is there even a CLOSE command?
In my case, there is no server used, because this is private work that I cannot trust to be placed on any public server since I do not want anyone to have access to it (and by anyone I include the owner of the public server). I have thought about setting up a server on one of the two machines (home or office) but that would require one of these computers to be always on, which again I would rather not have. So, in my case, my only alternative is to move the fossil file from computer to computer – so that the ‘master’ relocates all the time between two points. And, proper procedure for most applications would be to close a file, transfer it, and then re-open it. But, maybe fossil is more lenient... I don’t know. So, are you saying, that if I keep both repo versions (work and home) open all the time, and simply copy over (from the backup) the related fossil files, there won’t be any corruption on either site? And, I suppose instead of open (at the start of the day), I should be doing what exactly? FOSSIL REV to update the current checkout from the just updated FOSSIL file which would appear like a revert on the other side? Or, an UPDATE? And, what if I’m on different branches? Is this guaranteed to work correctly without creating any unpleasant side effects, from simple forks, etc., to the most serious of which would be a corruption of the repo and loss of work (and not only one day’s)? OK, maybe I do not need the functionality I asked for but can someone explain what would be the equivalent work flow between two different machines where there is no common server, and the FOSSIL file is at any moment replaced with a new file (from the other machine?) Currently, my process is this: LOOP: FOSSIL OPEN ... code changes ... FOSSIL COMMIT FOSSIL CLOSE transfer repo file to other machine, and copy it over the previous version goto LOOP From: Richard Hipp Sent: Monday, October 27, 2014 1:11 PM To: Fossil SCM user's discussion Subject: Re: [fossil-users] FOSSIL ALL On Mon, Oct 27, 2014 at 6:58 AM, Tony Papadimitriou <to...@acm.org> wrote: I have several repos open at the same time, not always the same ones. Before I swap computers (home <=> work) I would like to close all open repos on one site, and take a backup to take to the other site. "Close" them? Why do you want to do that? It seems to me that all you really need to do is ensure that all changes have been committed, which can be accomplished using "fossil all changes". Presumably, all of your repos have a default sync partner - probably a "master" repository on a server someplace. (At least, that is the way I work things. I have 35 projects currently going on my desktop, all of which are mirrored on one of two servers I control in the cloud.) In that case, all you need to do before leaving work is "fossil all changes" to look for uncommitted changes. Then when you get to home, just do "fossil al sync" to pull all the changes from work down to your home machine. Nothing needs to be closed. When heading back to work, just do "fossil all changes" on your home machine to make sure you have committed everything, then "fossil all sync" when you get back to the office. The scenario above is exactly why I invented "fossil all". :-) -- D. Richard Hipp d...@sqlite.org -------------------------------------------------------------------------------- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
