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.
On Mon, 04 Jul 2005 10:48:27 -0300, Daniel Lapolla <ldlapolla at yahoo.com> wrote: >Daniel Lapolla wrote: >> Daniel Lapolla wrote: >> >>> Sometimes we need to assemble a working copy that consists of a tag >>> (baseline) and a set of branches. >>> >>> The normal procedure was to check out (or update) with -r <tag_name> >>> -j <1st_branch_name>. >>> >>> Then we used to switch the modified/added files to the <1st_branch_name>. >>> >>> To retrieve the second branch, we used to do an update -j >>> <2nd_branch_name>, switch the modified files to <2nd_branch_name> and >>> so on for each other branch in the set. >>> >>> But now cvsnt seems to override the branches' sticky tags with the >>> directory tag <tag_name>, and ends up retrieving the old revision. >>> >>> Is this new behavior intentional or its a bug added some time ago? >>> >>> We are using server 2.5.01.1910 and client 2.0.51d. >>> >>> TIA >>> Daniel >> >> >> Oh... I forgot to tell... I did a little test here. I renamed the "Tag" >> file inside CVS' directory and the update worked as expected (in that >> directory only). This was discussed (at length) when it happened and was later also fixed. You should not use such an old testing release when reporting problems... /Bo (Bo Berglund, developer in Sweden)