From owner-freebsd-current@FreeBSD.ORG  Fri Jul 11 06:46:30 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 38A6F37B401
	for <current@FreeBSD.ORG>; Fri, 11 Jul 2003 06:46:30 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C1E7343FD7
	for <current@FreeBSD.ORG>; Fri, 11 Jul 2003 06:46:29 -0700 (PDT)
	(envelope-from kan@FreeBSD.org)
Received: from freefall.freebsd.org (kan@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6BDkTUp020180
	for <current@FreeBSD.ORG>; Fri, 11 Jul 2003 06:46:29 -0700 (PDT)
	(envelope-from kan@freefall.freebsd.org)
Received: (from kan@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6BDkTai020179
	for current@FreeBSD.ORG; Fri, 11 Jul 2003 06:46:29 -0700 (PDT)
Date: Fri, 11 Jul 2003 06:46:29 -0700
From: Alexander Kabaev <kan@FreeBSD.ORG>
To: current@FreeBSD.ORG
Message-ID: <20030711134629.GA15149@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.1i
Subject: Re: HEADS UP: GCC 3.3.1 - HOLD
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jul 2003 13:46:30 -0000

This is HEADS UP form people who haven't upfdated theri systems yet.
Please hold your updates as there are reports of a kernel being broken
with symptoms I haven't seen on my testing machine. Either I mismerged
something or something else did go wrong. I am lookign into this right
now and will keep you posed on progress.

--
Alexander Kabaev