On 9 October 2013 12:16, Brettschneider Falk <[email protected]> wrote: >> In a ticket comment, it seems that in order to reference the changeset 45 >> with a Traclinks, I have to write [changeset:45/reponame]. >> The only way to avoid that would be to have a global default repository. >> >> Would it be a good approach to have the default repository set to the >> repository of the ticket project ? If yes I will open a >> feature request on this. > > The Trac module accessing the SVN repos and also the TracLink system is > totally independent of the ticket system or > even roadmap or projects. > > It's up to the Trac user to organize the sources and projects. > Imagine you have one SVN repository, and your projects use sources from > subdirs of that single repository. Or you have > project 1 using sources of repo A,B,D,G and project 2 using sources of repo > B,C,D,E,F. > Likely, you use one repo per project, but this is a very special use case. > > I suggest that you always use TracLinks like this [123/reponame] in a world > of multiple repositories. TracLinks [123] make > sense in single repo environments.
Ok that makes sense. I understand know why managing multiples project with Trac was so long to come: not as easy as it looks like given the number of different possible configuration ! Regards, -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/groups/opt_out.
