[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:18:55 -0400

>From address@hidden  Wed Feb 14 01:44:29 2001
>Return-Path: <address@hidden>
Received: from ( [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Wed, 14 Feb 2001 01:44:23 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14SiTw-00024K-00; Tue, 13 Feb 2001 11:39:12 -0500
Received: from ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14SiSt-0001yr-00
        for <address@hidden>; Tue, 13 Feb 2001 11:38:07 -0500
Received: from ( [])
        by (8.9.1/8.9.1) with ESMTP id LAA22551;
        Tue, 13 Feb 2001 11:37:53 -0500 (EST)
Received: from (address@hidden [])
        by (8.8.6 (PHNE_17190)/8.8.5) with ESMTP id LAA07285;
        Tue, 13 Feb 2001 11:37:50 -0500 (EST)
Received: (from address@hidden)
        by (8.9.0/8.9.0) id LAA00943;
        Tue, 13 Feb 2001 11:37:46 -0500 (EST)
Message-Id: <address@hidden>
Subject: Re: Timestamp race avoidance in do_update()
To: address@hidden (Brad Chisholm)
Cc: address@hidden, address@hidden
In-Reply-To: <address@hidden> from "Brad Chisholm" at Feb 12, 1 05:52:48 pm
From: address@hidden (Larry Jones)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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: Tue, 13 Feb 2001 11:37:46 -0500 (EST)
Status: O
Content-Length: 995
Lines: 23

Brad Chisholm writes:
> Just to make sure I understand, CVS is sleeping to ensure that any post-CVS
> process which might modify the file must also change the timestamp.  This
> is necessary, because the CVS client relies on the timestamp to determine
> whether a file has been modified.  (i.e. if the current timestamp of the
> file matches the timestamp stored in the Entries file, then the client
> will consider the file unchanged, even if the contents have actually changed).

Exactly.  As I said in the thread you quoted, you should send all of the
file information first and then a single update command, not a separate
update command for each file.  Also, the current development version no
longer sleeps when in server mode; it is up to the client to do it

-Larry Jones

Monopoly is more fun when you make your own Chance cards. -- Calvin

Info-cvs mailing list

reply via email to

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