On Mon, Oct 27, 2014 at 7:48 AM, Tony Papadimitriou <to...@acm.org> wrote:
>
> 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?
>
Correct. Just copy the *.fossil files.
The _FOSSIL_ or .fslckout files in your local checkout are another matter.
Just leave them be. Don't try to copy those. But the *.fossil
repositories can be freely copied from one machine to the other.
Or, if you want, you could "clone" the repository to another repository on
your backup (a USB thumb drive, perhaps?). Just set auto-sync to "off" so
that it doesn't automatically sync on every update and commit. And use the
"file:" scheme instead of "http:" when creating the clone and syncing.
fossil sync file:/backup/myrepo.fossil
Either way works.
>
> LOOP:
> FOSSIL OPEN ---- Skip this step. Not needed.
> ... code changes ...
> FOSSIL COMMIT
> FOSSIL CLOSE ---- Skip this step. Not needed.
>
> transfer repo file to other machine, and copy it over the previous version
> goto LOOP
>
> *From:* Richard Hipp <d...@sqlite.org>
> *Sent:* Monday, October 27, 2014 1:11 PM
> *To:* Fossil SCM user's discussion <fossil-users@lists.fossil-scm.org>
> *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
>
>
--
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
