RE: Official sources vs. RCVS

[Cameron, Steve]

I wrote:
         [...]
>  Derek Price wrote:
> 
>       Okay, it applied and compiled fine, but I've already found a bug:
> if
>       the executable can find the tag in val-tags, it won't provide an
> error
>       when the specified tag doesn't exist in a file.In the above case, it
>       seems to be assuming the requested file is empty.  This seems to
> happen
>       regardless of whether a magic tag is specified.
>       [smc]  [...] .  
>       What does that mean?  [...]
                I've thought about it a bit more: suppose you have two
modules, 
                module_a and module_b.  One of the modules exists on a
branch,
                say "BranchA" and one does not, so the files in one module
contain
                the branch tag "BranchA", while the files in the other
module do not.

                And of course BranchA is in val-tags

                So suppose you go into the directory in your sandbox which
contains
                the module_b, which is not on BranchA and do this:.

                cvs update -r BranchA.origin

                What should happen?

                What currently happens is something like this:

                cvs update: Makefile is no longer in the repository
                cvs update: blah.h is no longer in the repository
                cvs update: blahblah.c is no longer in the repository

                Just the same as if you did:

                cvs update -r BranchA

                with either the patched or unpatched cvs 1-11, so
                I think it's working right after all, or at least just as 
                right as 1.11 does.   Or am I still missing something?.