I suspect the root problem is that I'm not thinking in the CVS paradigm --
I'm a programmer with a timeshare in the CM hat, here, not a CM person.
So here's what happened:
All the files included in our 4.4.1.0 release are tagged v4_4_1_0 at the
appropriate revision.
Files modified since that t
Mullican, Catherine writes:
>
> All the files included in our 4.4.1.0 release are tagged v4_4_1_0 at the
> appropriate revision.
> Files modified since that time which should be included in the 4.4.1.1
> release are tagged v4_4_1_1 -- but only changed files are currently tagged.
That's the probl
Larry Jones wrote:
>Mullican, Catherine writes:
>
>
>>All the files included in our 4.4.1.0 release are tagged v4_4_1_0 at the
>>appropriate revision.
>>Files modified since that time which should be included in the 4.4.1.1
>>release are tagged v4_4_1_1 -- but only changed files are currently t
