On Tuesday 30 January 2007 13:25, Peter Dimov wrote: > IMHO implementing multiple repositories is the sole responsibility of > the vcs backend
Imho this is the wrong way to go. By simply introducing a virtual toplevel directory and virtual directories for each branch/repository, one loses important information (besides the problem that there can't be nameless branches). A branch/repo simply is not identical to a toplevel dir. All source: wiki links for example have to carry that faked toplevel dir, but for anyone not knowing the setup of that trac, this remains unclear. Instead the repository should be specified by a mapable prefix similar to the way the InterTrac links work (e.g. separated by a colon, as in "source:my-branch:[EMAIL PROTECTED]"). This way, the source links stil carry the branch/repo information, but now in an explicit way. If there's a mapping between these prefix and the branches/repos somewhere, one can even move/rename repositories, extract sub-projects, and the like. (We want to have that going hand-in-hand with multiple projects support, don't we?) Regards, Thomas -- Thomas Moschny <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
