[Top][All Lists]

[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:04:47 -0400

>From address@hidden  Thu Feb  1 17:36:03 2001
>Return-Path: <address@hidden>
Received: from (address@hidden [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Thu, 1 Feb 2001 17:36:02 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14OFAu-0003ju-00; Thu, 01 Feb 2001 03:33:04 -0500
Received: from ([])
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14OF8g-0003j2-00
        for <address@hidden>; Thu, 01 Feb 2001 03:30:47 -0500
Received: from ( [])
        by (8.8.8/8.8.5) with ESMTP id AAA10398;
        Thu, 1 Feb 2001 00:30:36 -0800 (PST)
Received: (from address@hidden)
        by (8.8.8/8.8.5) id AAA02346;
        Thu, 1 Feb 2001 00:30:35 -0800 (PST)
Message-Id: <address@hidden>
From: address@hidden (Paul Sander)
In-Reply-To: <address@hidden>
X-Mailer: Mail User's Shell (7.2.6 beta(4)+dynamic 03/19/98)
To: address@hidden, address@hidden
Subject: Re: Locking Command
Cc: address@hidden
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: <>,
List-Id: Announcements and discussions for the CVS version control system 
List-Unsubscribe: <>,
List-Archive: <>
Date: Thu, 1 Feb 2001 00:30:34 -0800
Status: O
Content-Length: 1968
Lines: 47

Why bother with locking at all when you have timestamps?  For copy-out
operations where you can identify all versions in advance (which you can
do with timestamps), you don't need locks because the versions can't be
altered after they've been committed.

So, wrap your "cvs checkout" command in a script that supplies the -D
option with the current time.  If you expect to be able to modify and
commit the files without doing an "update -A" first, then have your
script remove the sticky state from the CVS Entries files after the
checkout completes.

For copy-out operations where all affected versions can be identified in
advance (ideally by version number, or timestamp, but version tags can be
used only if they're not concurrently updated), you can even go straight to
the repository and safely copy out versions using straight RCS, assuming
that CVS uses the same copy/modify/rename method to update the ,v files,
and not even bother with CVS' directory level locking.  

--- Forwarded mail from address@hidden

Why do you want to do such a thing?

Assuming you really do want what you're asking, wrap CVS such that whenever you
do a checkout, it'll move the repository to a location accessible only by you.
Your shell script will also record where the moved repository is so that future
operations will work.  I know this is a very hackish solution, but yours is a
very odd request.

address@hidden on 2001.01.30 22:54:43

To:   address@hidden
cc:   (bcc: Noel L Yap)
Subject:  Locking Command

    I'm working under a CVS project. When I checked out the source
and do some modification at that time no one should have the access
to the Repository. For this what I have to do. Is there any Locking
methods. If there tell me how to Lock files in CVS.

--- End of forwarded message from address@hidden

Info-cvs mailing list

reply via email to

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