From owner-freebsd-current Sun Nov 1 14:52:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20288 for freebsd-current-outgoing; Sun, 1 Nov 1998 14:52:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20282 for ; Sun, 1 Nov 1998 14:52:11 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id XAA01606; Sun, 1 Nov 1998 23:48:54 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Sun, 1 Nov 1998 23:48:54 +0100 (CET) From: Leif Neland To: Jeroen Ruigrok/Asmodai cc: Dmitry Valdov , freebsd-current@FreeBSD.ORG, Peter Wemm Subject: Re: kernel compile problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It could be implemented by modifying using cvsupd's ability to check out > > the version of the tree as it were on a certain time. > > > > The committer sends it a command/file/signal, and then new additions > > made after that time is not seen by someone who requests the latest > > versions. > > Exactly, does the term commit-relay express the idea completely? > Nah, not really... I don't understand the word... > > 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. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message