From owner-freebsd-stable Fri May 15 09:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21836 for freebsd-stable-outgoing; Fri, 15 May 1998 09:30:25 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21662 for ; Fri, 15 May 1998 09:30:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id JAA04764 for ; Fri, 15 May 1998 09:30:10 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: stable@FreeBSD.ORG Subject: Hello.....? Whomever broke -stable, are you going to fix it? Date: Fri, 15 May 1998 09:30:09 -0700 Message-ID: <4760.895249809@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Doing nightly build attempt for 3.0-980515-SNAP at Fri May 15 02:27:15 EDT 1998 Updating source tree... Making release... Release build of 3.0-980515-SNAP was a success at Fri May 15 07:27:14 EDT 1998 Doing nightly build attempt for 2.2-980515-SNAP at Fri May 15 07:27:15 EDT 1998 Making release... Release build of 2.2-980515-SNAP was an abject failure. The 2.2 snaps have been dying for 4 days now due to the sh breakage I already pointed out yesterday. If I don't hear anything in the next 12 hours I'm going to fix it myself and that will essentially entail backing out anything that looks suspicious from -stable, so do it now or see your changes backed out. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message