From owner-freebsd-current Sun Nov 1 15:19:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24008 for freebsd-current-outgoing; Sun, 1 Nov 1998 15:19:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24000 for ; Sun, 1 Nov 1998 15:19:55 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from diabolique.ninth-circle.org ([195.121.59.131]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA54E3; Mon, 2 Nov 1998 00:19:48 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 02 Nov 1998 00:23:42 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Leif Neland Subject: Re: kernel compile problem Cc: Peter Wemm , freebsd-current@FreeBSD.ORG, Dmitry Valdov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 01-Nov-98 Leif Neland wrote: >> > After everything is committed, the committer removes the lock. >> >> Why the commiter? Make it so that the cvsupd places a lock temporarily >> whenever >> a commit finds place. Then after the person is through with his or her >> commits >> it makes all those updated files available to the public for cvsup. Make it >> so >> that the daemon does the work and not the commiter. This saves hassle. >> > Not having done any committing, I guess a committer could make several > changes in different parts of the tree, in smaller chunks. Only the > committer will know when all the chunks have been committed. So only the > committer should unlock the changes. > > As equivalent in the Oracle database, one session could make several > changesin different table, but only after issuing a commit, all changes > get visible for other sessions, and all at the same time. That's what I meant =) Except the Daemon (in this case the Oracle database) allowed the changes. That's what I meant with the CVSupd too... The committer is expected to comm it. The Daemon is expected to handle all the administivia of the allowance/versioning. Hope this makes it clearer for the both of us. And the others offcourse =) --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl Junior Network/Security Specialist FreeBSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message