Mark wrote: > Just to let you know that I have finished the review of these pages.
Thanks for your great work, it's very much appreciated. > Note - even though I have read all the documentation - I am still a > little confused with the repository changes needed to upgrade from > 0.11. For example I have mercurial repositories connected to my 0.12 > release (without any kind of post-commit-hook) and everything seems to > work fine - the documentation was leading me to think that it should > not work. Or is it the case that it wont work without the hook for SVN > repos? The Mercurial backend currently doesn't do any caching, so strictly speaking no sync operation is necessary, hence no post-commit hook. This is going to change in the future, so we don't want to advertise it. Subversion uses caching, so it requires syncing. This can be done in the post-commit hook (the most efficient method), or at every HTTP request (the 0.11 method, inefficient and pretty much unusable with more than one repository). Moreover, we now have an extension point for "repository changes" (IRepositoryChangeListener, IIRC) that is triggered by the post-commit hook. No hook -> no notification of repository changes for plugins. -- Remy
signature.asc
Description: OpenPGP digital signature
