RE: concurrent development, two repositories

[Arthur Barrett]

Jeffery,

 

I just recently also came across a scenario where this was required.

 

As Pierre pointed out the best alternative is to use vendor branches instead and have the other developers send a complete tarball.

 

Importing vendor branches and doing bulk merges is an administration task - do not attempt to use Eclipse/WinCVS/TortoiseCVS/etc for that.  For administration tasks use the command line cvsnt or cvs.

 

Regards,

 

 

Arthur

 

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of Jeffery Lin
Sent: 08 November 2005 16:50
To: address@hidden
Subject: concurrent development, two repositories

I am part of a software project that involves two development teams working on the same code base. The MAJOR catch is that these two teams (for legal, corporate, and whatever reasons beyond my control) cannot share the same CVS repository. So we develop separately, then every few weeks they send us a "patch" and I have to merge the two code bases.

What I currently do is put their code on a branch then use the Eclipse Synchronization view to compare our trunk to the branch. Usually there are about 1,000 differences, and I go through each one manually to decide whether we need the change merged into the trunk.

Is there an easier way to do this?!

Jeff