On Wed, Apr 8, 2015 at 5:02 PM, <[email protected]> wrote: > Is anyone interested in a diff with this functionality? I don't mind > digging into the code, but I don't want to waste my time if it goes > against a core idea of Fossil. I'd just like the option of using it > with nothing external-facing other than SSH. >
i'm (still) on medical leave with a disabled hand, so won't say more than: there are a couple old posts in the list archives explaining various pitfalls involved with autosync of ticket changes. Short form: it introduces all sorts of new error conditions (primarily network-related) which currently don't exist. The same applies to changes made in the wiki. (That's not to say that it'd be impossible.) > > For developers, this process works great. Autosync performs flawlessly, > > and we go about our business. However when filing tickets through the > > UI, a "fossil sync" seems to be mandatory. My request is that tickets > > also get pushed via an autosync function on 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 [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
