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.
Hi, We work with the branch per change request policy, but we create the branch in the affected files only. To fetch a change request branch we used to do the following: 1. cvs update -P -A -d -jbr_cr_12345 2. in wincvs, select all "red" files and do an cvs update -P -C -r br_cr_12345 This procedure used to left the working copy with the latest head revision in all the files, except the ones with the branch br_cr_12345, that would be in the branch with the sticky tag. Since we upgraded our server to 2.5.01.1976, this procedure does not work anymore for files that were initially added to the branch. For those files we get the following message: cvs server: warning: new-born newfile.txt has disappeared Is there a better way to accomplish that? Is it possible to change this cvsnt behavior? Current setup: Server 2.5.01.1976 / Client: Wincvs 2.0.2 (CVSNT 2.0.51d) Old Setup: Server 2.5.01.1910 / Client: Wincvs 2.0.2 (CVSNT 2.0.51d) TIA Daniel