Christian Boos <[EMAIL PROTECTED]> writes: > In the TracGuide, there's the TracBrowser, TracChangeset and > TracRevisionLog pages > which explain what you can do. Also, the integration is achieved by > the way of the > TracLinks in the wiki syntax, which enables you to "talk" about your > changesets > or source files from any part of the system (tickets, wiki pages, etc.) > > Lastly, there's a contributed post-commit-hook script for Subversion, > which will comment on and otherwise manipulate your tickets in Trac > depending on what has been written in the changeset message.
So this is all nifty, but I have set up fairly elaborate permissions for my repositories (using webdav and http authentication, soon to be https). Is there a way I can prevent Trac from exposing the parts of the repository that are supposed to be private or restricted? -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
