On Wed, May 08, 2013 at 10:20:07AM +0200, Stephan Beal wrote: > On Wed, May 8, 2013 at 9:34 AM, Oliver Friedrich <[email protected]> wrote: > > > We now have discovered that wiki-pages seem to be not synchronized, but > > only always used from the last edit. That leads us to some difficulties, > > editing a wiki-page on both front-repositories - loss of first edit. > > > > How is the best way to handle this missing functionality. How would you > > approach on this? > > > > The wiki pages do sync but do not partake in branching/merging - the last > one wins but all historical versions are still there. There is no www UI > for diffing between wiki page versions, but the JSON API is capable of > doing it. Here's an example: > > http://fossil.wanderinghorse.net/wikis/cpdo/?page=cpdo > > (That's a custom wiki front-end using a fossil backend via the JSON API) > > - click on the Timeline tab (near the right) > - click on the version number of one of the wiki page changes. > > Because the wiki pages are internally the same thing as files, they could > theoretically be extended to support tagging/branching/etc., but so far > there has never been any motivation to do so.
Friederich has a very good point on this. In wiki pages or tickets, you can't never be sure you have lost information in a synchronisation. Information is dropped silently. One thing is not be able to merge; the other is losing information silently. Very annoying. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
