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.
Tony Hoyle wrote: > Daniel Lapolla wrote: > >> >> Yes and no, because the resulting working copy has the br_cr_12345 tag >> sticked in ALL the files, not only the ones pertaining to the branch... >> >> And there is another (worse) problem: if I want to compose an working >> copy with 2 or 3 branches for example, I cannot use -f, and if these >> branches contain failes in the same situation as newfile.txt, I'm >> unable to compose the WC... > > > If you're trying to do it with multiple branches simultaneously you're > really asking for trouble... checking out multple branches is good in a > limited number of circumstances - yours doesn't sound like one of them > to me.. you're trying to do all the tracking that CVS does automatically > by yourself, and creating problems in the process. The ability to work with "mixed" working copies WAS one of the good features of cvsnt... It seems it's gone now and will not come back... > > In this case I suggest CVS isn't the tool you should be using. I'm not > sure what is - no version control tool I'm aware of works in that manner. > > Tony Well, at least before 2.5.01.1976, cvsnt used to do that... In my humble opinion, the ability to create mixed working copies is a good thing. In fact build 1976 still allow you to do that (except for the files that only exist in the branch). Regards Daniel.