CODEWITHSUNDEEP
svnbranchbranching-and-mergingvisual-sourcesafe
animgr
animgr

Reputation: 71

SVN branching - how can I only keep branched files?

In our enterprise project we used to use VSS. Our project for 6 customers were single source, so we only needed to keep a "fullVersion" and "branched" directories for our version managements. In order to get the sources of customer1, we first get the fullversion and then branched for customer1(it was been replaced to general sources).

We have migrated to SVN. But the question now is that if I want to have the same functionality, I need to keep the whole project in "fullVersion" and in every "branches". becuase switching in SVN does the same functionality. Am I right? Please help me to find the solution to this problem, so I can keep one general source, and only branched files of different customer?

Upvotes: 0

Views: 33

Answers (1)

Lazy Badger
Lazy Badger

Reputation: 97282

In common case - yes, branch in Subversion contain full tree of project with unmodified, contrary to trunk, and branch-related changes. In you case in means: every change in core must be replicated (by merge) in customer-branches

Depending from structure of project (and version of SVN - you have fresh SVN, isn't it?) you can think about using SVN externals in order to link (stored somewhere) different branched-files from common single core-codebase

Upvotes: 1

Related Questions