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.
Henrik Wahlberg wrote: > 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. > -----------------Example---------------- > Aim. Build a release for Costumer_A based on the general release tagged > IFS_711 > On the root of my sandbox I'd update to IFS_711: > > cvs -q update -P -r IFS_711 > > 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. I can see what you're doing here, but I probably would use a tag IFS_711_A for the /complete/ set of files of release IFS_711 for customer A. I'm not a fan of partial tagging... Gerhard