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.
I was looking for a parameter to the update command, (when updating to a sticky revision) to leave files not carrying the tag as they are. It should be somewhat similar to the -f option, but instead of taking the latest from head when the file isn't carrying the tag in question, it should leave the files as they are (possibly sticky tagged to some other revision). Oliver Giesen suggested me to post a rfe. Hope it's the correct place and my explanation is adequate. -----------------Example---------------- Aim. Build a release for Costumer_A based on the general release tagged IFS_711 The file CosIniFile.java is in rev 1.66 on head, and carries the tag IFS_711 on rev 1.60. On the root of my sandbox I'd update to IFS_711: cvs -q update -P -r IFS_711 which would bring the source tree to this release. (and in particular CosIniFile to rev 1.60) then I was hoping to be able to do something similar to: cvs -q update -P -f -r Costumer_A to have those file carrying the "Costumer_A" tag updated, leaving other files at the IFS_711 revision. Unfortunately (in my situation) the other files are replaced with head. P.S. A bit to my surprise, after doing these two steps, WinCVS is indicating files not carrying the Costumer_A tag, as stickyTagged to Costumer_A, a tag not existing on any of them, whereby the next normal update would remove most of the files. TIA. Best regards Henrik Wahlberg