Bug is tagging the head of a branch head???

[Fouts Christopher ()]

I have CVS v1.11.14.

I create a development branch of the HEAD.
I know the branch was created successfully since I can do a 
cvs co -r b_dev_01_02, and cvs status -v on one of the files
and get...

File: file1             Status: Up-to-date

   Working revision:    1.6     Tue Apr 13 21:27:40 2004
   Repository revision: 1.6     /cvsroot/sample/dir1/file1,v
   Sticky Tag:          b_dev_01_02 (branch: 1.6.2)
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        b_dev_01_02                     (branch: 1.6.2)
        t_pre_dev_01_02                 (revision: 1.6)


If I want to tag the head of a newly created branch (with no work
committed to it yet), I just do a 

        > cvs rtag -r b_dev_01_02 t_pre_dev_01_02_xx sample

correct? Straight forward enough, or so it seems. Now when I do 
a checkout of the tagged files,

        > cvs co -r t_pre_dev_01_02_xx sample

and do a cvs status -v on one of the files, it shows the tag sticking
to the HEAD revision, NOT the branch head revision. 

File: file1             Status: Up-to-date

   Working revision:    1.6     Tue Apr 13 21:27:40 2004
   Repository revision: 1.6     /cvsroot/sample/dir1/file1,v
   Sticky Tag:          t_pre_dev_01_02_xx (revision: 1.6)
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        t_pre_dev_01_02_xx              (revision: 1.6)
        b_dev_01_02                     (branch: 1.6.2)
        t_pre_dev_01_02                 (revision: 1.6)

Is this a bug???

--------------------------------------
Chris T Fouts