info-cvs
[Top][All Lists]
Advanced

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

(no subject)


From: root
Subject: (no subject)
Date: Mon, 13 Aug 2001 05:19:35 -0400

>From address@hidden  Wed Feb 14 07:26:09 2001
>Return-Path: <address@hidden>
Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164])
        by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
HAA15527
        for <address@hidden>; Wed, 14 Feb 2001 07:26:08 +0900
Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org)
        by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
        id 14Snrk-0001BL-00; Tue, 13 Feb 2001 17:24:08 -0500
Received: from ho.egroups.com ([64.211.240.236])
        by fencepost.gnu.org with smtp (Exim 3.16 #1 (Debian))
        id 14Snpe-0000O2-00
        for <address@hidden>; Tue, 13 Feb 2001 17:21:58 -0500
X-eGroups-Return: address@hidden
Received: from [10.1.10.120] by ho.egroups.com with NNFMP; 13 Feb 2001 22:21:55 
-0000
From: address@hidden
To: address@hidden
Subject: Strict Locking for checkouts
Message-ID: <address@hidden>
User-Agent: eGroups-EW/0.82
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
X-Mailer: eGroups Message Poster
X-Originating-IP: 200.32.16.25
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Id: Announcements and discussions for the CVS version control system 
<info-cvs.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Archive: <http://mail.gnu.org/pipermail/info-cvs/>
Date: Tue, 13 Feb 2001 22:21:53 -0000
Status: O
Content-Length: 765
Lines: 22

        I need to stablish a strict lock on each checkout on my repository,
and then, when a user try to checkout a locked file, I need to denie
access.

        As far as I see, I can a do a cvs admin -l to make a lock and use
rcslock.pl in commitinfo to deny access for checkins... I have 2
question. 

1- How can I automate the strinct locking creation? I cant not rely on
users for this, I need some automated method to lock on each checout.

2- As I see rsclock only works for checkins.. how can I do to make
this work on checkouts? In my implementation a user can not checkout a
file if another user is working on it.

Thanks in advance!


_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs




reply via email to

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