Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [e4-dev] Using cvs import in therepository/CommonBuildInfrastructure

Do you have other suggestions?
CVS Repository e35 is a given.
Repository e4 is more free to choose, but must
be synchronized against its ancestor (e35)
frequently, and should look like a CVS repository
to the build infrastructure...
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member

From: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrey Tarantsov
Sent: Wednesday, November 12, 2008 8:38 PM
To: E4 Project developer mailing list
Subject: Re: [e4-dev] Using cvs import in therepository/CommonBuildInfrastructure

1.) git cvsimport e35-cvs -->  e35-git
2.) git cvsimport e4-cvs  -->  e4-git
3.) git init e4-merged-git
   git pull e35-git --> e4-merged-git
   git pull e4-git  --> e4-merged-git

Took a few moments to figure what you mean, rather unusual. But yes, should be possible. (Still, for me it sounds very brave. :)


Back to the top