From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Would nobody please finish what he's doing. Date: Tue, 19 Jun 2007 13:00:21 -0400 Message-ID: References: <20070619121908.GA2606@muc.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1182298305 20895 80.91.229.12 (20 Jun 2007 00:11:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 20 Jun 2007 00:11:45 +0000 (UTC) Cc: Alan Mackenzie , Eli Zaretskii , emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 20 02:11:42 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1I0nnQ-0003lQ-Nc for ged-emacs-devel@m.gmane.org; Wed, 20 Jun 2007 02:11:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I0nnP-0002d2-SM for ged-emacs-devel@m.gmane.org; Tue, 19 Jun 2007 20:11:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I0nnL-0002Zi-Il for emacs-devel@gnu.org; Tue, 19 Jun 2007 20:11:35 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I0nnJ-0002VO-Hn for emacs-devel@gnu.org; Tue, 19 Jun 2007 20:11:34 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I0nnJ-0002Uv-Ah for emacs-devel@gnu.org; Tue, 19 Jun 2007 20:11:33 -0400 Original-Received: from toq5.bellnexxia.net ([209.226.175.27] helo=toq5-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I0nnI-0001Wl-51; Tue, 19 Jun 2007 20:11:32 -0400 Original-Received: from ceviche.home ([70.55.143.156]) by tomts16-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20070619170021.ERQM1673.tomts16-srv.bellnexxia.net@ceviche.home>; Tue, 19 Jun 2007 13:00:21 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 13544B4B9B; Tue, 19 Jun 2007 13:00:20 -0400 (EDT) In-Reply-To: (Andreas Schwab's message of "Tue\, 19 Jun 2007 18\:02\:04 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux) X-detected-kernel: Solaris 8 (1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:73366 Archived-At: > Every CVS operation needs a lock, if only to make sure that nobody is > modifying the meta data while you are reading it. *Note (cvs)Locks::. > *Note (cvs)Concurrency::. There's theory and then there's practice. As mentioned, without a read lock, anonymous checkout risk getting slightly inconsistent data, but IIRC the possible inconsistency is very minor (and transient: fixed by the next "cvs update"). The CVS-level (i.e. module-level) metadata is basically inexistent, so the main issue is the RCS-level (i.e. file-level) metadata: this is updated pretty much atomically (by writing the new RCS data into a new file and then moving it into place). Many CVS repositories have used such unlocked anonymous access with good results. Stefan