Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hello around the world ! Does anybody know whether cvsnt supports "virtual branches" ? Let's say that developer forks branch B from the HEAD at revision 1.10 of file F. The file was modified several times so current rev. is 1.15. There was no modification in the branch B for this particular file. The developer decided to do update (merge) from HEAD to keep branch B up to date. CVS creates new revision of the file F in the B branch after the merge - 1.10.1.1 which is actually the same as 1.15. (in our case it happens for binary libraries, so the RCS file is growing and growing :-((( ) Wouldn't be possible to specify at the beginning at revision 1.10 a "virtual branch" that would become real branch if and only if somebody commits to the branch ? Until that, any update of branch B returns HEAD of file F, because the real branch not exist yet. If such a features does not exist, how to handle a case of third party libraries, that are used over several developer branches but changing in HEAD only ? How to prevent CVS to create their copies per each merge form HEAD to any branch and together keep history so if one would like to check out historical version from particular branch, he/she would obtain the correct revision of the library - the one that used to be HEAD at that time. Thanks for any ideas, JP _____________________________________________________________________ This email message, including any attachments, may contain confidential and proprietary information for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any use, copying or dissemination of this message is strictly prohibited. If you received this message in error, please notify Brooks Automation, Inc. immediately by reply email or by calling Brooks US Headquarters at +1 978-262-2400. Then delete this message from your system, without making any copy or distribution. Thank you.