From owner-freebsd-current  Wed Nov 17 11:18:50 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP
	id CE7CF14EB7; Wed, 17 Nov 1999 11:18:42 -0800 (PST)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA02423;
	Wed, 17 Nov 1999 20:18:42 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
Date: Wed, 17 Nov 1999 20:18:41 +0100
Message-ID: <2417.942866321.1@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@freebsd.org>
Subject: Bumping libstdc++ version number
MIME-Version: 1.0
Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa"
Content-Description: Blind Carbon Copy
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

------- =_aaaaaaaaaa
Content-Type: message/rfc822
Content-Description: Original Message

To: committer@freebsd.org
Subject: Bumping libstdc++ version number
From: Poul-Henning Kamp <phk@freebsd.org>
Date: Wed, 17 Nov 1999 20:18:41 +0100
Message-ID: <2417.942866321@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
MIME-Version: 1.0


The core team has discussed the issue of bumping the libstdc++
version numer because of the compiler upgrade:

Yes, we do have a rule saying ``only one bump per release'',
and that rules still stands.  But no rule without exception:

Clearly what we're looking at here deserves a version number
bump, and therefore -core hereby gives David O'Brien
permission to do so.

for -core,

Poul-Henning Kamp


--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!

------- =_aaaaaaaaaa--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message