[Trac-tickets] [The Trac Project] #1082: Support for subversion
sub-repositories
The Trac Project
noreply at edgewall.com
Sat Dec 25 21:23:01 EST 2004
#1082: Support for subversion sub-repositories
---------------------+------------------------------------------------------
Id: 1082 | Status: new
Component: project | Modified: Sat Dec 25 21:22:57 2004
Severity: normal | Milestone: 0.9
Priority: normal | Version: 0.8
Owner: daniel | Reporter: eric.brown at propel.com
---------------------+------------------------------------------------------
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.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/1082>
The Trac Project <>
More information about the Trac-Tickets
mailing list