On Mon, 13 Mar, Richard Hipp wrote: > > The upgrade is simple. Just replace your current fossil executable > with a new one. Everything should work exactly as it did before. > There are no incompatibilities. The only difference is that Fossil > 2.1 will read and write the latest repositories whereas Fossil 1.x > will not.
Thanks for the encouragement, it turned out that it exactly worked like this. We did not yet find any breakage in command line usage or output. Nice job. :-) However one concern was raised: What, if for some reason, some fossil user has to go back to version 1.x from 2.x. I just did a short test with a "fossil-1 rebuild" on a fossil-2 repository. The only thing that in my quick test survived was the initial empty checkin, but not the following content checkins. Another "fossil-2 rebuild" however brought back the contents. So, do I assume that once you start working with fossil-2 on the repository, you cannot "rebuild back" to version 1, even if you do not (intent to) use new fossil 2 features? So, to be on the safe side one would have to take a backup of the fossil in version 1 state? Or is there any "go back to version 1 format" emergency way? Greetings, Stefan -- Stefan Bellon _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
