Re: is that possible the same code under two different subversion service provider?

On 02/21/2013 01:15 PM, Thorsten Schöning wrote:
> Guten Tag frame,
> am Donnerstag, 21. Februar 2013 um 17:19 schrieben Sie:
>
>> Suppose our project tree look like:
>
>> project/aaa
>> project/bbb
>
>> Currrently, the whole project tree is under subversion control
>> provided by company A. In the same time, I also want to put the sub
>> directory project/aaa under subversion control provided by company
>> B. The reason for doing that is somebody abroad is cooperating with
>> us and his work is in project/aaa. He does not have the access to
>> the company A's repo. He can access company B's repo. So is there a
>> way to let project/aaa under two different subversion? When he
>> changes the code inside project/aaa, he checks in to company B's
>> central repository, I pull out his change from company B to my local
>> area. Then I check in his code change into company A's repo on behalf of him. Is this doable?
>
> Sounds like a vendor branch to me, where the source of the branch was
> a dumped part of your repo, imported into the other. But afterwards
> everything else should fit vendor branch best practice.
>
> http://svnbook.red-bean.com/en/1.7/svn.advanced.vendorbr.html

I was thinking the same thing, though I wouldn't bother with the dump/load
initializing step -- a history-free export/import should be sufficient.

Note that I recently rewrote that section of the book a bit (I never really
liked what I'd come up with in earlier book versions). You can see the
nightly build version of that information at:

http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html

(Feedback about the book should go to svnbook-dev_at_red-bean.com, though, not
to this list.)

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development