Repository design question

Hi all,

I have a base toolkit that I use to build websites, which I have in a
local repository. Each website that's based on it ends up containing
some changes that I want to put back into the toolkit, and others
that need to remain local customizations.

In the CVS days the repositories were kept totally separate and
commits were made twice where appropriate. I can continue to do
that, but I was hoping there might be a better way to model this in
Subversion.

I could make each website a branch from the trunk, but then I'm
concerned about making sure that local changes stay local and don't
accidentally get merged up.

How do others handle this type of scenario?

thanks,

janine

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 19 21:42:46 2007