Re: help with cvs import

[Kevin Rodgers]

Kevin Rodgers wrote:
> I tried using cvs admin command as described in the "Reverting to the
> latest vendor release" section of the manual, but to no avail.

I'm pretty sure that worked before.  Isn't the following evidence that
it did?

symbolic names:
        build-18: 1.3
        build-17: 1.3
        build-16: 1.3
        TINYMCE_2_0_5: 1.1.1.5
        build-15-va: 1.3.0.2
        build-15: 1.3
        build-14: 1.3
        build-13: 1.1.1.4
        build-12: 1.1.1.4
        build-11: 1.1.1.4
        build-10: 1.1.1.4
        build-9: 1.1.1.4
        TINYMCE_2_0_4: 1.1.1.4
        build-8: 1.2
        build-7: 1.2
        build-5: 1.2
        build-4: 1.2
        build-3: 1.2
        build-2: 1.2
        VA1_0: 1.2
        build-1: 1.2
        TINYMCE_2_0_3: 1.1.1.3
        TINYMCE_2_0_2: 1.1.1.2
        MOXIECODE_DIST: 1.1.1
        a_0_1: 1.1.1.1
        IHS: 1.1.1

That indicates to me that after the vendor tag TINYMCE_2_0_3 import,
I made modification 1.2, which was used for subsequent builds 1- 8.
Then the vendor tag TINYMCE_2_0_4 import was used for builds 9-13,
when I made modification 1.3, used in subsequent builds 14-15.

But vendor tag TINYMCE_2_0_5 import was not used for builds 16-18 --
shouldn't `cvs admin -bMOXIECODE_DIST` have taken care of that?

Thanks,
--
Kevin Rodgers