info-cvs
[Top][All Lists]
Advanced

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

Re: Help regarding lock on default branch


From: Mark D. Baushke
Subject: Re: Help regarding lock on default branch
Date: Sat, 24 Jan 2004 19:35:48 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Karthik,

This issue has been raised multiple times in the info-cvs mailing list.
You may find review of the list useful.

For an example of one of the threads, follow this link:

  http://mail.gnu.org/archive/html/info-cvs/2002-05/msg00149.html

There have also been proposed patches to allow for changes in how the
commitinfo trigger is called such that the branch information is
included for each file. See

  http://mail.gnu.org/archive/html/info-cvs/2004-01/msg00024.html

for more information if you are willing to consider patching your cvs
sources with Claus Henriksen's suggested patch.

        Good luck,
        -- Mark

Karthik Kumar <address@hidden> writes:

>    For our project we are using CVS. And we have created a separate
> branch dev - wherein goes all the modifications of the source code.
> But I dont want anyone to touch the default branch  ( in the sense, I
> want to disable all 'commit's to the default branch ). 
>    I did the following - 
> 
> 1) Checked out the default branch. 
> cvs get <my_module>
> 
> 2) Tried to lock it . 
> 
> cvs admin -l 
> 
> 3) But still I can commit other files from here. What am I missing
> here to lock the default branch. 
> 
>   Thanks for your help in this regard. 
> 
> Cheers
> Karthik. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD4DBQFAEzmU3x41pRYZE/gRAhfAAKC78hczjGPjA+vxBzGa70K8Xb2bVgCXd82q
OLwAnvQ9JtWR3pI0xPFVBQ==
=1gZ7
-----END PGP SIGNATURE-----




reply via email to

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