Re: problem with tagged files

[David Fuller]

Well, first your process is not right.  A tag says 'all the file revs
with this tag go together', so by tagging only the 2 files you are
saying that they are the only files needed.  Can you clarify why you
don't want the other files tagged?  I can't think of a good reason.

The only way the tester in your scenario could get things the way you
want with the process you are using then developer X would have to tell
tester Y what files to get updates on.  

-- David F.

JM Murillo wrote:
> 
> This is the situation:
> 
> 1-The developer "X" has a working copy of the module "M".
> 
> 2-The developer "X" has modified two files in his working copy (the files
> are "f1" and "f2")
> 
> 3- "X" performs a commit of "f1" and "f2" files to the repository.
> 
> 4- "X" puts the same tag "T" to the "f1" and "f2" files.
> 
> 5- The tester "Y" has another working copy of the module "M".
> 
> 6- "Y" needs to update his working copy with the files with the "T" tag.
> 
> 7- If  "Y" perform "cvs update -r   T " in the root directory of his working
> copy then "f1" and "f2" are updated, but the other files in his working copy
> are removed.
> 
> 8- If   "Y" perform "cvs update -f -r T " in the root directory of his
> working copy then "f1" and "f2" are updated, but the other files are
> retagged with the "T" tag.
> 
> 9- Is there any way to update the working copy of "Y" with the "T" tagged
> versions of "f1" and "f2" without removing any file and without retagging
> any file?
> 
> 10- I know there is a way to do this updating individually each file "f1"
> and "f2" ("cvs update -r T f1 f2") , but "Y" doesn't know which files were
> modified.
>