[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: locking of release

From: David Penn
Subject: Re: locking of release
Date: Fri, 22 Sep 2000 14:15:35 +0800

where can i find the patch? will u pls provide url for me? Thanks in advance!
I update my CVS to 1.11, the bug is still in it.

David Penn
Shanghai Inst., Huawei Tech. Co.
P.R. China
----- Original Message ----- 
From: <address@hidden>
To: <address@hidden>
Sent: Monday, September 04, 2000 2:59 AM
Subject: Re: locking of release

> Hello,
> This is known bug in CVS when you use "cvs admin -l" to lock the 
> revision. It will actually lock both "" and "1.1" 
> revisions. You have to unlock the file using rev tag.
> cvs admin -u -r1.1.1.1 myfile.c
> cvs admin -u -r1.1 myfile.c
> The bug actually happens after you edit and commit the first change 
> to a file. Commit will create a new revision, which is locked also.
> If you are trying achieve "restricted editing" functionality 
> then "cvs edit -c" is better way of doing this. This will allow 
> editing only when there are no other "editors" at the same time. 
> However, you need a patched version of CVS. The latest release of 
> CVSNT includes this patch already.
> Best regards,
>  Mika Nieminen
> --- In address@hidden, "Dhiradj Ramautarsing" 
> <address@hidden> wrote:
> > Release files in CVS. When a release source is 
> locked, it
> > cannot be unlocked. The error message is that multiple revisions 
> are locked,
> > so CVS does not know which version to unlock. This only occurs for 
> release
> > This is probably a known bug. Who knows an acceptable 
> solution?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]