Austin Bingham wrote:
> I've done some looking around, but haven't found a definitive answer to
> this question. Basically, we're looking for a way to make, at least
> notionally, a partial branch. That is, we want to create a branch for only
> a few files in our project. However, we want for all of the other files in
> the project to remain "shared" between the original and the branch. That
> is, changes made to shared file from either point of view (branch or
> original) would be reflected in the other. Changes made to non-shared
> files should remain isolated to the particular branch on which they were
> made.
>
> It seems that we can achieve some of this effect using external
> definitions. Basically, we'd have a directory containing all common code
> and one directory for each branch (containing just the branched stuff).
> Then, we could use dummy/proxy directories with external defs that
> associate the correct brached code with the shared code.
>
> In any case, I hope I've communicated what we're trying to accomplish.
> Really, I'm trying to avoid the need to do manual change propagation in
> situations when I know that certain files in the branches should always
> stay synchronized. Any thought or ideas would be greatly appreciated.
Branch your entire project, then check out the trunk and use 'svn
switch' to switch the sections of the tree you're looking to modify over
to the branch. You're then in a position to test the changes you're
making on the branch with the rest of your project as it exists on the
trunk.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 29 16:31:00 2004