All of this gives me a headache. Talk about drifting away from the elegance of Fossil: distributed revision control with tickets and a wiki in a single binary. Let's get back to the original program, folks! You have so many other choices for bloatware....
:-) On Tue, Sep 14, 2010 at 1:19 PM, Wolfgang <rat...@stumvolls.de> wrote: > Yusuf X <ys1...@...> writes: > > > > > Hi, I have a need to build a repository once it's checked in. A handy > > feature would be to trigger a script (i.e., "ant build_repo1.xml") > > once code is pushed to the server for a particular repository. It > > should not be a large change; if it's not in, shall I add it? > > > > Hi > > ANother problem, based on the distributed nature of fossil, is the possible > existence of forks! > > Maybe it would be a better way, to have a daemon, polling the fossil repo > and > forcing your action, when an event occurs. Therefor you can easyly ask > timline.rss. This could be done for example with wget from the shell. > > best regards,Wolfgang > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Michael Barrow michael at barrow dot me
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
