From owner-freebsd-arch Thu Jan 31 5:32:27 2002 Delivered-To: freebsd-arch@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 2A7A837B400 for ; Thu, 31 Jan 2002 05:32:13 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16WHMk-000KyT-00; Thu, 31 Jan 2002 15:35:02 +0200 From: Sheldon Hearn To: Terry Lambert Cc: arch@FreeBSD.org Subject: Re: Adding support for a global src tree serial number In-reply-to: Your message of "Thu, 31 Jan 2002 05:20:36 PST." <3C5944A4.4927F812@mindspring.com> Date: Thu, 31 Jan 2002 15:35:02 +0200 Message-ID: <80628.1012484102@axl.seasidesoftware.co.za> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 31 Jan 2002 05:20:36 PST, Terry Lambert wrote: > If I have serial number X, and two commits are started > A,B, and the commits complete as either A,B or B,A, is the > serial number X+1, X+2 or some other number? Always X+2, since two commits have followed since the previous serial number X. > What is the interaction with the serial number and CVSup > or explicit checkouts? Poor, according to Ruslan. This seriously undermines the value of this serial number. > Is the serial number updates at the start of a checkin, > or at the end? At the end. > Is it possible for the serial number to not match the code > atomically? Not in the master repository, but (again, according to Ruslan) this is possible with cvsup mirrors. > Is the increment on a per file, or a per checking basis? > (I could perhaps see per file working better, since there > are per file writer locks to prevent simultaneous commits). Per checkin. > I don't really see how you could make atomicity guarantees > that would keep this serial number from getting off-by-1 in > one direction or the other, or off-by-N, in the case of a > CVSup in the middle of a large commit (since repository > replication is also non-atomic, at present). Yeah, I didn't realize that CVSup isn't at all interested in the checkin process. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message