Lack of hooks is a hassle for me too. Wrapper scripts don't meet the need - especially on the server side. Part of the power of hooks is that you don't have to replicate the effort of parsing the command line to know what is being done.
An example: I have a regression system running and when commits happen on the release branch of the regression code I'd like the regression run area brought up to date. This is very easy with a hook on commit. Right now I have to run fossil update in a crontab every five minutes. Maybe there is a better way even without hooks? ----- Original message ----- > * Jeremy Anderson <[email protected]> [20110719 06:18]: > > Out of curiosity, why are you converting from mercurial? > > 1) plain C, single binary > 2) integrated wiki & ticketing > > The big minus for me which still keeps me on mercurial for some stuff is > the lack of hooks for significant events (commit/update, push/pull). > > qvb > -- > pica > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
