On Wed, 2011-01-12 at 11:19 +0100, Christian Boos wrote: > Elegant I don't know, but the old way was not scalable when you have > multiple repositories. Even for a single repository, the cost of > checking for a synchronization can be non-negligible, not to mention the > fact that if your request actually triggers a synchronization, you'll > notice the delay. By using the post-commit hook, the synchronization > only happens once when needed, and "off-line". And you have ways to set > the post-commit hook so that it fires asynchronously, so that it won't > block the "svn commit" client operation.
Perhaps a bit of an aside. Perhaps not. I just moved a Trac setup to a new system. Along the way, I had the trac part up before the subversion repos were set up. They were configured in trac. But the repositories themselves were not available. OOC, I looked at the timeline, and none of the subversion changes were there. Including some that I know were there before the move. I have hooks in the subversion repos. I would have thought that the changes communicated by the hooks would have resulted in some data being stored locally in trac, and that those changes would still be listed by trac in the absence of the repos. When the repos were once again available, all the commit messages returned. Perhaps this is indicating that I have something incorrectly configured? Or is this way one would expect things to be? -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
