From owner-freebsd-current  Sun Dec  8 23:40:19 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id XAA13640
          for current-outgoing; Sun, 8 Dec 1996 23:40:19 -0800 (PST)
Received: from tfs.com (tfs.com [140.145.250.1])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id XAA13633
          for <freebsd-current@freebsd.org>; Sun, 8 Dec 1996 23:40:18 -0800 (PST)
Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP
	id m0vX0IS-0003wtC; Sun, 8 Dec 96 23:38 PST
Received: from critter.tfs.com (localhost.phk.dk [127.0.0.1]) by critter.tfs.com (8.8.2/8.8.2) with ESMTP id IAA15525; Mon, 9 Dec 1996 08:40:33 +0100 (MET)
To: George Michaelson <ggm@connect.com.au>
cc: Chuck Robey <chuckr@glue.umd.edu>, freebsd-current@freebsd.org
Subject: Re: siguing into current from a random version 
In-reply-to: Your message of "Mon, 09 Dec 1996 11:09:03 +1000."
             <15134.850093743@connect.com.au> 
Date: Mon, 09 Dec 1996 08:40:32 +0100
Message-ID: <15523.850117232@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <15134.850093743@connect.com.au>, George Michaelson writes:
>
>Snaps are good but the timelag between snaps and interesting state in current
>is bad. If you're saying that for any given SUP state you can go from the
>last snap to current without tripping over any non-reversable states, well
>and good.  I don't think you're saying that :-)

Well, the snaps are supposed to happen about every other month or so...

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@tfs.com           TRW Financial Systems, Inc.
Power and ignorance is a disgusting cocktail.