Re: commiting a sticky file

snip..............................
> Risman>> Do you mean track differences between the tags? As long as you
> have the two tags, you can track the differences, though if the tags
> never change then neither will the differences. Remember that if one of
> the tags were a branch tag, that will move as long as new revisions are
> committed to that branch.


ok, i think i have it. and again thanks, Mark.

i've been editing and checking in a few files in the branch and
all was going well until this one file.

all i've sampled look like:
===================================================================
File: RELEASENOTES.txt  Status: Up-to-date

   Working revision:    1.103.2.3
   Repository revision: 1.103.2.3       /home/cvs/repository/rcp/
RELEASENOTES.txt,v
   Commit Identifier:   ocPo4COp3n9HHMXt
   Sticky Tag:          RCP_5_0_1 (branch: 1.103.2)
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        RCP_5_0_2                       (revision: 1.103.2.2)
        RCP_5_0_1                       (branch: 1.103.2)
        RCP_6_0_CVN                     (revision: 1.105)
        RCP_5_0                         (revision: 1.103)
        RCP_4_9_2                       (revision: 1.102)
        .....

except this one:
===================================================================
File: RCP.iap_xml       Status: Locally Modified

   Working revision:    1.6.2.1
   Repository revision: 1.6.2.1 /home/cvs/repository/rcp/tools/
install_anywhere/conf/RCP.iap_xml,v
   Commit Identifier:   veSNKconrX7O6oSt
   Sticky Tag:          RCP_5_0_1 (revision: 1.6.2.1)
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        RCP_5_0_2                       (revision: 1.6.2.1)
        RCP_5_0_1                       (revision: 1.6.2.1)  ????
        RCP_6_0_CVN                     (revision: 1.9)
        RCP_5_0                         (revision: 1.6)

appears to have escaped being part of the branch.