#1082 closed defect (duplicate)
Support for subversion sub-repositories
Reported by: | Owned by: | daniel | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | project | Version: | 0.8 |
Severity: | normal | Keywords: | subversion svn project |
Cc: | eric.brown@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
My subversion repository is shared across many projects so we can share code. In the timeline, searching, etc., I only want to see changes relevant to my project.
In the [trac] section of the config file, there should be an item for "repository_dirs". This should be a list of directories relevant to a trac project. The default would be "/". In more complicated repositories, it might be one of the following:
- "/project1"
- "/project1,/shared"
- "/trunc/project1,/branches/project1_1923"
It would be great to allow wild-cards, but that seems much lower priority.
My repository is not arranged as "/{trunc,branches,tags}", but as "/(project1,project2,project3)/{trunc,branches,tags}". I doubt this is very rare. However, if it is, arrangements like "/trunc/project1,/branches/project1,/tags/project1,/trunc/project2"… are probably common. These cases would really want some system of wild cards possibly. It is rather impossible to completely anticipate how users might organize their repository. It would probably be easiest to provide some facility like I've suggested here and let users know how they can reorganize their repository to use trac with sub-repositories. The nice thing about subversion is that moving things isn't nearly as painful as with cvs.
Attachments (0)
Change History (2)
comment:1 by , 20 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:2 by , 19 years ago
Milestone: | 0.9 |
---|
Yes, this has been raised multiple times before. See #586