Hi,
is it possible to use the new svn merge feature across repositories?
- or can I disturb any of the attended repositories this way (svn cp was at
least in history not designed for cross-copy, so that I disturbed my
repository this way).
My planned pattern is to some degree comparable to the "vendor-branch"
approach as documented in http://svnbook.red-bean.com/en/1.1/ch07s05.html
But I'd like to avoid the long way with svn_load_dirs.pl performing repeated
imports instead of applying incremental changes (diffs).
An alternative solution might be based on extracting a classic DIFF-File
with "svn diff -ra:b .... > change_a_b.diff" and applying it in a working
copy of the other repository with classic "patch -p0 <change_a_b.diff".
The best solution would be direct "svn merge" to apply the delta from repoA to
a working copy of repoB.
The exact scenario:
a) two groups of derivative projects from same root project
b) RepoA should get hosted by people, who should not get access to
variants in RepoB
c) use new SVN feature mirroring to host RepoA_Mirror at same server as
RepoB
d) keep main trunk of RepoA_Mirror in sync with RepoB
( changes can happen at both sides )
I don't like to cause some problems in either repository by experimenting
with "svn merge", when this can heavily disturb a repository by
cross-repo-merging (I had already some bad problems some year ago, when I
tried "svn cp" across repos).
Thanks for any hints,
Achim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-04 13:37:24 CEST