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

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

Just as an idea: Did you have a look at things like git2svn etc.?
Your cooperator with access to company B could simply work on it's
own repo, implemented with git or whatever, and you could import the
changes he made into your repo like a vendor branch again, just using
git2svn or else. Id don't think its necessary that your cooperator
commits into another subversion repo.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow