From owner-freebsd-current Thu Feb 24 22:41:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 4627237BE10; Thu, 24 Feb 2000 22:41:27 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id AAA26245; Fri, 25 Feb 2000 00:41:26 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-105.max1.wa.cyberlynk.net(207.227.118.105) by peak.mountin.net via smap (V1.3) id sma026241; Fri Feb 25 00:41:16 2000 Message-Id: <3.0.3.32.20000225004006.00a0a100@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 25 Feb 2000 00:40:06 -0600 To: Kris Kennaway From: "Jeffrey J. Mountin" Subject: Re: Marathon Cc: current@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.20000224182319.007ece90@207.227.119.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:33 PM 2/24/00 -0800, Kris Kennaway wrote: >On Thu, 24 Feb 2000, Jeffrey J. Mountin wrote: > >> So when is this event scheduled to end, so we can go for a test drive? >> >> 57^H^H61 commits to -current and counting... > >The last message to show up in the series said Mark was finished and about >to collapse unconscious, so I guess that means "let the bug reports >begin"! Please check that your bug hasn't already been reported before >mailing, though, eh? Making Mark pass out again in fright due to 3000 new >messages in -current when he wakes up won't help anyone, least of all him >:-) Looks like 61 messages for 209 deltas is the final total, but may have missed a few messages, since I didn't find the "done" part. No to mention my CVSup output shows DG following right behind him. 'Cept it looks like Brian F impersonating him. No matter, build in progress. Dependant ports to follow. Hmmm... maybe should have toasted the RSAref port, then build, then install and see if the "just works" part mentioned does work.... Why not.... in progress... kudos/complaints to follow. ;) As for checking first. Usually wait a day before even building, but tend to get a bit more adventuresome around release time. Otherwise my build dies and it's usually fixed or at least spoken for. 8-/ Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message