From owner-freebsd-current  Wed May 14 02:05:36 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA27668
          for current-outgoing; Wed, 14 May 1997 02:05:36 -0700 (PDT)
Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA27629
          for <current@FreeBSD.ORG>; Wed, 14 May 1997 02:05:26 -0700 (PDT)
Received: (from bsdcur@localhost)
          by shadows.aeon.net (8.8.5/8.8.3) id MAA02853;
          Wed, 14 May 1997 12:05:01 +0300 (EET DST)
From: mika ruohotie <bsdcur@shadows.aeon.net>
Message-Id: <199705140905.MAA02853@shadows.aeon.net>
Subject: Re: CVSUP date = ?
In-Reply-To: <Pine.BSF.3.96.970511143759.253A-100000@bsampley.vip.best.com> from Burton Sampley at "May 11, 97 02:48:52 pm"
To: burton@bsampley.vip.best.com (Burton Sampley)
Date: Wed, 14 May 1997 12:05:01 +0300 (EET DST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Greetings,
> Can some1 running -current give me the date and time -current was last
> able to build without puking up errors.  I tried CVSUPing Friday night,

well, i built it last time at sunday, and i do it always as

time make -k world > logi 2>&1 & ; sleep 1 ; tail -f logi

(sleep is needed usually, you dont need to time it)

and only thing it reported as broken was the same old contrib failure (tcl)
so it doesnt really matter at all...

the '-k' is usefull with -current coz if it's broken, it builds, then i
can check what was broken, lately it havent been anything fatal...

*knock* *knock* *knock*

i wouldnt suggest '-k' with kernel though. it compiled well.

and last time i havent gotten any probs? well, the tcl thing has been
around atleast weeks, probably over a month.


mickey