Date: Mon, 2 Nov 1998 00:34:26 +0100 From: Eivind Eklund <eivind@yes.no> To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>, Leif Neland <leifn@swimsuit.internet.dk> Cc: Peter Wemm <peter@netplex.com.au>, freebsd-current@FreeBSD.ORG, Dmitry Valdov <dv@dv.ru> Subject: Re: kernel compile problem Message-ID: <19981102003426.04544@follo.net> In-Reply-To: <XFMail.981102002342.asmodai@wxs.nl>; from Jeroen Ruigrok/Asmodai on Mon, Nov 02, 1998 at 12:23:42AM %2B0100 References: <Pine.BSF.4.05.9811012343110.1311-100000@gina.swimsuit.internet.dk> <XFMail.981102002342.asmodai@wxs.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 02, 1998 at 12:23:42AM +0100, Jeroen Ruigrok/Asmodai wrote: > 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 =) Sorry - this discussion is getting sort of useless. It _is_ possible to handle this within cvs/cvsup, but if we are to do that, we will have to create a lock for a single commit, and have cvsup grab the previous version if this lock is present (a commit is in progress). Making this will be a large set of changes both to cvs and cvsup. Due to the time available to the relevant developers, I believe this is to be very unlikely to happen. Besides this, I believe it would be less work to replace all of cvs and cvsup than to implement this within the present framework (if we allow the replacement to work against a real database instead of working with a self-made database). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981102003426.04544>