From owner-freebsd-stable  Thu Oct  2 23:22:19 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA22347
          for stable-outgoing; Thu, 2 Oct 1997 23:22:19 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca14-03.ix.netcom.com [204.32.168.67])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA22342
          for <freebsd-stable@freebsd.org>; Thu, 2 Oct 1997 23:22:15 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id XAA12545; Thu, 2 Oct 1997 23:21:55 -0700 (PDT)
Date: Thu, 2 Oct 1997 23:21:55 -0700 (PDT)
Message-Id: <199710030621.XAA12545@silvia.HIP.Berkeley.EDU>
To: dg@root.com
CC: rgrimes@GndRsh.aac.dev.com, jkh@time.cdrom.com, andrsn@andrsn.stanford.edu,
        freebsd-stable@freebsd.org
In-reply-to: <199710021544.IAA21048@implode.root.com> (message from David Greenman on Thu, 02 Oct 1997 08:44:23 -0700)
Subject: Re: CVSUP vs. SNAPS
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 *    No, "2.2" refers to the branch, not to a release. I think we make that
 * pretty clear.

Yep.  Besides, what are we going to call 3.0-CURRENT before the 3.0
release then?  (2.9999-CURRENT? :)  It's going to be 3.0-CURRENT for a
while after the release, and we'll have the same "problem".  That is
not going to be solved by confusing the release and branch names.

Satoshi