On 17 March 2010 17:06, Darren Pearce-Lazard wrote:

> But, if you did want to keep them separate yet still 'share' some code, you
> could always 'link' the repositories using the svn:externals property. Note
> that this is purely a Subversion feature so will not mean that issue lists,
> etc, will be amalgamated.

  Thanks.  But the goal is to get rid of the administrative overload.
And as I am not a professional system admin, I am more and more
concerned with the backups...  If I understand correctly, this
solution does not solve those problems, does it?

  Regards,

-- 
Florent Georges
http://www.fgeorges.org/

-- 
You received this message because you are subscribed to the Google Groups 
"Project Hosting on Google Code" 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/google-code-hosting?hl=en.

Reply via email to