On Mon, Nov 3, 2014 at 6:42 AM, Andy Bradford <amb-fos...@bradfords.org> wrote:
> Thus said jungle Boogie on Sun, 02 Nov 2014 18:03:39 -0800: > > > Should you expect to see the wiki changes on the cloned copy or will > > they always/only be on the project that did fossil init? > > Fossil Wiki content synchronizes just like other Fossilized content. ...except that wiki (and ticket) changes do not get autosynced: one has to manually sync/push/pull in order to get everything transferred. > rate, if you are just making source commits, then autosync should take > care of automatically pushing the content to the server. If not, you can > always manually cause a sync with fossil sync or fossil push. > Note that an autosync triggered for a commit/update will include wiki/ticket bits, but editing the wiki is not enough to get it to sync - a manual push/sync is required unless one is also doing other work with will force an autosync (e.g. "commit" would normally do this). > Local wiki changes have to be manually synchronized after you have made > changes: e.g. fossil sync. > That'd be the easiest way to do it, i think - simply run sync after saving wiki changes. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
