svn - Merge without Branching from the same code-base? -


We did not manage this small development project through the version control system. Two people were working on the original code-base, so the original code-base had two separate copies. Say these copies "Copy A" and "Copyb".

Now I tried to make an SVN store for these two copies. I put "Copy A" in the trunk and put "Copy" in a branch called "Brachab".

Then two developers started working on these two storey paths. ("Trunk" and "branch b").

Then we had to get these two branches together, but it seems that the right result was not found.

Is it necessary to merge the same "code-base" branches into the next phase?

There was no single "code-base" in my case, committed to two different SVNs from "Copy" and "Copyb".

This is best if two branches are the same starting point.
You can "merge" two unrelated branches in the SVN (section ""):

merge unrelated sources

If you ask SVN to get a second Merge to compare two URLs which is not related to, a patch will still be generated and applied for copying your work, but no merged metadata will be created. There is no general history between the two sources and the future. Mergers are dependent on that common history.

Note that this will be a situation where more efficient, because it is easy to set up two branches, each " copyA , and" copyB < / Code> "to remove the contents of the second branch (git" copyA will detect all names, moves and additions initiated by " copyB " " ). If you have created two unrelated branches in GIT, then you will still be able.

Comments