From owner-freebsd-current  Sat Jul  8 15:56:47 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id PAA08472
          for current-outgoing; Sat, 8 Jul 1995 15:56:47 -0700
Received: from haywire.DIALix.COM (root@haywire.DIALix.COM [192.203.228.65])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA08435
          for <freebsd-current@freebsd.org>; Sat, 8 Jul 1995 15:56:43 -0700
Received: (from news@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id GAA16167 for freebsd-current@freebsd.org; Sun, 9 Jul 1995 06:13:49 +0800
Received: from GATEWAY by haywire.DIALix.COM with netnews
	for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com)
To: freebsd-current@freebsd.org
Date: 9 Jul 1995 06:13:27 +0800
From: peter@haywire.dialix.com (Peter Wemm)
Message-ID: <3tmvu7$fo7$1@haywire.DIALix.COM>
Organization: DIALix Services, Perth, Australia.
Subject: Version numbers of the different branches?
Sender: current-owner@freebsd.org
Precedence: bulk

One thing that's bugged me for a while now, is that FreeBSD-current
announces itself as "2.0-xxxxxx", even though it's actually working
towards being FreeBSD-2.2

Not that it's a really big issue, but I wouldn't mind it being
consistant somehow.

How about making it either "2.2-BUILT-xxxxxx" or "2.X-BUILT-xxxxx" or
even "2.X-CURRENT-xxxxxx".

Of course, this means the newvers.sh file is going to have to be
branched into 2.0.5, 2.1 and -current..

Cheers,
-Peter