From owner-freebsd-arch Thu Jan 31 3:28:25 2002 Delivered-To: freebsd-arch@freebsd.org Received: from cisco.com (europe.cisco.com [144.254.52.73]) by hub.freebsd.org (Postfix) with ESMTP id E434237B402 for ; Thu, 31 Jan 2002 03:28:18 -0800 (PST) Received: from cobweb.example.org (dhcp-nic-val-26-117.cisco.com [64.103.26.117]) by cisco.com (8.8.8+Sun/8.8.8) with SMTP id MAA10922 for ; Thu, 31 Jan 2002 12:28:09 +0100 (MET) Received: (qmail 28462 invoked by uid 1000); 31 Jan 2002 11:28:50 -0000 Date: Thu, 31 Jan 2002 12:28:50 +0100 From: Marco Molteni To: arch@FreeBSD.org Cc: Sheldon Hearn Subject: Re: Adding support for a global src tree serial number Message-ID: <20020131112850.GB28361@cobweb.example.org> References: <79300.1012474898@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79300.1012474898@axl.seasidesoftware.co.za> User-Agent: Mutt/1.3.25i 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 Hi Sheldon, the only drawback I see to your approach is that the serial number you are proposing is dateless, so folks will probably ask for a date too: > This problem was introduced in serial number 11809 and was > corrected in serial number 11832. My suggestion is to use a serial number bound to the date the serial number was generated, something like 20020223123435XXXX yyyymmddhhmmss with XXXXX set to the precision you consider appropriate, and the date being GMT. Or maybe something like 20020223-XXXX yyyymmdd where XXXX is the number of changes made in that day up to this change. One difference is that with your proposal two successive serial numbers have a difference of 1, for example 11833 - 11832 = 1, while with mine you loose this. My 0.02 euros marco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message