Re: commiting a sticky file

sparkylee <[email protected]>
Newsgroups gmane.comp.version-control.cvs.general
Organization http://groups.google.com
Message-ID <0981c592-7fd6-4f66-9212-80b93b04f302@v37g2000prg.googlegroups.com>
CORRECTION. i make a super simple repository to check out your
suggestions
and don't know 1st time, but this time it worked. i created the
branch, updated,
edited and committed with no problem.

i think my problem in the original for-real repository, is that i'm
trying to commit a sticky revision,
not a sticky branch.  over there i never did an update -r
<branchname>; i just
checked out what i thought was a branch, but was just a tag i guess.

argh!!!

i'm not even sure anymore what i did.
i'm lost.
here's the cvs status -v output for the real file that i'm trying to
commit (to the branch):
===================================================================
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_2 (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)
        RCP_4_9_2                       (revision: 1.5)
        RCP_4_9_1                       (revision: 1.4)
        RCP_4_9_0                       (revision: 1.4)


yeah, under Existing Tags:   there isn't a branch.

so how about if i check out the RCP_5_0_2 tag,
then:
$ cvs tag -r RCP_5_0_2 -b RCP_5_0_2

and then
$cvs up -r RCP_5_0_2

then edit and commit files from there?

lee
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.