Hi Erik, The two following regex works fine with your repository:
branch_re = ^(?P<branch>[^/]+/(?:(?:tags|branches)/[^/]+|trunk))(?:/(?P<path>.*))?$ branch_re = ^(?P<branch>[^/]+/(?:branches/[^/]+|trunk|tags))(?:/(?P<path>.*))?$ The first regex shows all the branches, but it can generates wide revtree as each "tagged" release appears in a dedicated branch. If you have a lot of 'tags' in the selected time range, you'll end up with a wide revtree. The second regex considers all the tagged releases as part of the same branch, which generates a narrower revtree, but somewhat "hides" the tagged releases. I don't use the tags/ directory, but I guess it would be nice to enhance the revtree so that single revision branches such as 'tag' branches are better rendered... Anyway, an important point: > > BTW, note that several fixes have been fixed for Trac 0.11 > > (RevtreePlugin for 0.10.x is not maintained). I found a stupid bug in the RevtreePlugin that I've fixed for 0.11 (v0.5.0.1). I've back ported the fix in the version for 0.10 (v0.4.7.1), but I've not tested it so it may fails. Let me know. Without this fix, you won't be able to use the Revtree plugin with your repository. Cheers, Manu --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
