RE: can not lock a branch.

[Li, James]

Hi Larry,

Either cvs status -v call71 or more /export/cvs/build/emailor/call71,v I can find TEST_BRANCH. One problem I found is the working machine build(free BSD) cannot directly read file on cvs server machine pm2(Solaris). and RCS files are on pm2. What do you think? How to verify whether a RCS file is in the branch?

Thanks

-James

address@hidden:~/log/build/emailor > cvs st -v call71
===================================================================
File: call71            Status: Up-to-date

   Working revision:    1.1
   Repository revision: 1.1     /export/cvs/build/emailor/call71,v
   Sticky Tag:          TEST_BRANCH (branch: 1.1.2)
   Sticky Date:         (none)
   Sticky Options:      (none)

   Existing Tags:
        TEST_BRANCH                     (branch: 1.1.2)
        Rel-1-0-01010814_year_end       (revision: 1.1)
        Rel-1-0-00120618                (revision: 1.1)
        Rel-1-0-00111612                (revision: 1.1)

address@hidden:~/log/build/emailor > more /export/cvs/build/emailor/call71,v
/export/cvs/build/emailor/call71,v: No such file or directory

address@hidden:/export/cvs/build/emailor > more call71,v
head    1.1;
access;
symbols
        TEST_BRANCH:1.1.0.2
        Rel-1-0-01010814_year_end:1.1
        Rel-1-0-00120618:1.1
        Rel-1-0-00111612:1.1;
locks; strict;
comment @# @;

1.1
date    2000.11.15.02.46.00;    author alin;    state Exp;
branches;
next    ;
...
-----Original Message-----
From: address@hidden [mailto:address@hidden]
Sent: Thursday, March 08, 2001 8:28 AM
To: address@hidden
Cc: address@hidden; address@hidden; address@hidden;
address@hidden
Subject: Re: can not lock a branch.

Li, James writes:
>
> I do have TEST_BRANCH, but still can not figure out why cvs server cannot
> modify RCS file.

Not in those files, you don't -- CVS is telling you that it isn't there:

> RCS file: /export/cvs/build/emailor/call71,v
> cvs server: /export/cvs/build/emailor/call71,v: branch TEST_BRANCH absent

It might be useful to see what ``cvs status -v'' has to say about one of
these files.  Since CVS can't find the branch, there's nothing to lock
and thus CVS doesn't modify the RCS file.  Like I said, the message is
misleading; CVS could have modified the file if it wanted to, it just
didn't want to.  (I've checked in a change to clarify the message.)

-Larry Jones

OK, there IS a middle ground, but it's for sissy weasels. -- Calvin