From owner-freebsd-stable  Tue Oct  7 05:38:04 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id FAA22313
          for stable-outgoing; Tue, 7 Oct 1997 05:38:04 -0700 (PDT)
          (envelope-from owner-freebsd-stable)
Received: from silvia.HIP.Berkeley.EDU (ala-ca9-32.ix.netcom.com [207.93.143.96])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA22303
          for <freebsd-stable@FreeBSD.ORG>; Tue, 7 Oct 1997 05:38:01 -0700 (PDT)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id FAA16981; Tue, 7 Oct 1997 05:37:39 -0700 (PDT)
Date: Tue, 7 Oct 1997 05:37:39 -0700 (PDT)
Message-Id: <199710071237.FAA16981@silvia.HIP.Berkeley.EDU>
To: rgrimes@GndRsh.aac.dev.com
CC: dg@root.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu,
        freebsd-stable@FreeBSD.ORG
In-reply-to: <199710061520.IAA00369@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com)
Subject: Re: CVSUP vs. SNAPS
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Of all people to make this mistake.  Okay, I got this old box, I need
 * to grab a port for it, but I need to know if I want the port from
 * the 2.2, 2.2.1 or 2.2.2 cdrom.  Yea, I updated the box a couple times,
 * but it still should run any port from the correct cdrom, or for that
 * matter from the archives on the ftp site.

And you don't even know how to figure out when the last source update
was?  You have a bigger problem than figuring out which CDROM you
need, Rod. ;)  (Hint: "sysctl kern.osreldate")

Besides, the ports tree on the CDROM is not compatible with the
-stable in the future (how can it be?).  The compatibility goes in the 
opposite direction.

 * > Besides, if I show you a uname that says "3.0-CURRENT Fri Jan 18
 * > 13:56:36 PST 1998", can you tell whether it's before or after 3.0R?
 * 
 * Nope, not if Jordan insistes on continuing to equate a variable named
 * REVISION to a management tool called cvs and it's branch tags :-(

You are missing the point.  What I'm saying is that "3.0-CURRENT" is
going to mean both pre- and post-3.0 release even with your proposed
change.

Satoshi