[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Locking CVS
Re: Locking CVS
Mon, 11 Jul 2005 09:11:30 -0700
Thank you. I'm not sure what /bin/test represents? To be replaced with the
path to my proj?
----Original Message Follows----
From: "Mark D. Baushke" <address@hidden>
To: "S I" <address@hidden>
Subject: Re: Locking CVS
Date: Mon, 11 Jul 2005 08:49:43 -0700
Received: from colo-dns-ext1.juniper.net ([22.214.171.124]) by
mc3-f23.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 11 Jul 2005
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])by
colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j6BFnn912917;Mon, 11
Jul 2005 08:49:49 -0700 (PDT)(envelope-from address@hidden)
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])by
merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6BFnhj59521;Mon, 11 Jul
2005 08:49:43 -0700 (PDT)(envelope-from address@hidden)
X-Mailer: MH-E 7.84+cvs; nmh 1.0.4; GNU Emacs 21.3.1
Mail-Followup-To: info-cvs <address@hidden>
X-OriginalArrivalTime: 11 Jul 2005 15:49:51.0677 (UTC)
-----BEGIN PGP SIGNED MESSAGE-----
S I <address@hidden> writes:
> Hi everyone,
> I'm planning to lock cvs today getting ready for our release. I
> realize with certain version control software nowadays you don't have
> to lock the repo and the developers can continue with their work.
> However, we're imposing and enforcing a few days for freeze and to
> Our repository resides on a linux box with :pserver method access from
> WinXP CVS DOS and Tortoise clients. Could I just lock the repo by
> executing cvs admin -l or -L or do I have to download some perl
> module to accomplish this? I need to lock our CVS repository today.
> Three projects reside in the repository, is it possible to lock them
> selectively or would admin -l lock the entire repo?
admin -l will not really do what you want.
It would probably be simplest to add something to your CVSROOT/commitinfo
to do the job and fail whenever the :pserver: userid was used.
If you have an 'id' command that accepts the -u option, and for example
if the 'id -u' command printed 12345 as your userid, you could add
For cvs 1.11.x
ALL /bin/test `id -u` = 12345
For cvs 1.12.x you might want to use
ALL /bin/test `id -u` = 12345 && : %r/%p %s
This should return a non-zero error code for anyone other than the user
with the uid 12345 which we would presume you would use your own userid
and that you would be accessing the repository outside of the :pserver:
method or have arranged for your :pserver: usage to use your real userid
rather than masking it with the system userid.
Other methods exist for just locking a single branch (such as the main
trunk) using something like the contrib/cvs_acls file that comes with
recent cvs distributions.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
-----END PGP SIGNATURE-----