Tagging files based on existing tag. Why are fi les tagged with the new tag when the tag doesn´t not exist on some files

[Spilker, Jörg]

Hello,

during our developement, we are creating test releases by tagging all
modules with cvs rtag -F TEST_20040322 (for example). If a testing release
seems to be stable enough, we´re creating an official version from this
testing release. So we tag the latest test release with another tag for the
offical version with
cvs rtag -F -r TEST_20040322 RELEASE_20040330. Then we make a checkout cvs
co -r RELEASE_20040330 for all modules to compile the source. But there is
problem with added files after the last test release. These files don´t have
the TEST_20040322 tag, but they are tagged with RELEASE_20040330 (cvs issued
a warning about this). So the files go into the build process. We don´t want
to happen this. Maybe the -F (force) option is the problem here? I don´t
think so because -F should only handle the case when a tag already exists.

Greetings, Joerg