mengke Posted February 7, 2017 Report Share Posted February 7, 2017 It is said that one of the best practice to use VCS is to keep all submissions compilable, or more strictly, passes unit tests. However, consider this situation: I changed the version of xlinked subproject. The new code in subproject may have major changes, and may be incompatible with the codes in parent project. Theoretically I should modify code in parent project to fit with the subproject before submit. However, before I submit the xlink verison change, I cannot get the new code in subproject. How can I solve this dilemma? Thanks! Link to comment Share on other sites More sharing options...
calbzam Posted February 9, 2017 Report Share Posted February 9, 2017 Hi, We normally recommend to directly change the Xlinked repository from the parent one. This way, the Xlinked target changeset will be automatically updated. If somebody performed changes directly in the Xlinked repository, you will be requested to merge when commiting your changes. If your workflow require to modify the Xlinked repository from different sources, you may find useful the next blog post to handle this workflow: http://blog.plasticscm.com/2014/08/how-to-share-engine-repository-between.html Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.