Hi,
the qeustion is - is the design of your repositories the right way?
One repository can be used for let say - the same client and different
projects. There are many styles of repository design. You can set up
different users/permissions for different parts of your repository
etc. But I suppose
thanks Michal !
I agree with your comment about end users and that they cannot use the
trac tickets directly or it will screw everything up. my end users are
not coders or developers in any way so I agree they would be lost
with all the parameters.
so let me rephrase the question : how do you
with svn its very simple: use one repository and use as many trac
instances as you think is good. on the url the developers cannot
notice it it is one or more rep's.
-solo.
On 8/5/07, bert [EMAIL PROTECTED] wrote:
thanks Michal !
I agree with your comment about end users and that they
On Aug 4, 1:54 pm, bert [EMAIL PROTECTED] wrote:
hi,
i have a big app consisting of 4 svn repositories each with their own
trac instance.
they are not in a single repository because each of the 4 parts could
evolve at different development speeds, etc.
since the 4 parts make no sense to
