From owner-freebsd-current Sun Apr 9 01:24:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA11623 for current-outgoing; Sun, 9 Apr 1995 01:24:47 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA11604 for ; Sun, 9 Apr 1995 01:24:23 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de with SMTP (5.67b+/DEC-Ultrix/4.3) id AA27880; Sun, 9 Apr 1995 10:23:52 +0200 Received: by sax.sax.de (8.6.9/8.6.9-s1) with UUCP id KAA29102 for freebsd-current@FreeBSD.org; Sun, 9 Apr 1995 10:23:50 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.6.11/8.6.9) id JAA05262 for freebsd-current@FreeBSD.org; Sun, 9 Apr 1995 09:33:27 +0200 From: J Wunsch Message-Id: <199504090733.JAA05262@uriah.heep.sax.de> Subject: Re: closing bin/295 To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 9 Apr 1995 09:33:27 +0200 (MET DST) In-Reply-To: from "Richard Wackerbarth" at Apr 8, 95 05:12:24 pm Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1152 Sender: current-owner@FreeBSD.org Precedence: bulk As Richard Wackerbarth wrote: > > >> Agree. However, that points up a "problem" with the whole "SNAP-Release" > >> system. Perhaps we need to have some way of tracking just what version of > >> things is in that "release" eg: In the source files, we could/should > >> include the .ctm_status files that reflect the updates that had been > >> applied. > > > > >It's not actually related to CTM, so this is not free of potential > >raises. > ... With the advent of CTM, > I think it reasonable to use those numbers as the identification of interim > builds of -current. The problem is that the SNAP releases are cvs co'd separately. So they are not related to any particular CTM level, since CTM does its own cvs update (i think 4 times per day or so). The correct way is to first tag the tree and then cvs co it based on this tag instead of the ``current'' state. This is done for regular releases, but is unacceptable for SNAPs (due to the huge amount of sup and ctm traffic the tagging would cause). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)