From owner-freebsd-current Sun May 3 13:58:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26238 for freebsd-current-outgoing; Sun, 3 May 1998 13:58:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26226 for ; Sun, 3 May 1998 13:58:39 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA14880; Mon, 4 May 1998 07:00:15 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805032100.HAA14880@cimlogic.com.au> Subject: Re: VM changes broke SYSVSHM? In-Reply-To: <354C5194.8D8986B8@tdx.co.uk> from Karl Pielorz at "May 3, 98 12:14:28 pm" To: kpielorz@tdx.co.uk (Karl Pielorz) Date: Mon, 4 May 1998 07:00:14 +1000 (EST) Cc: tlambert@primenet.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Pielorz wrote: > Very true, but it's still amazing the amount of people I see who say "I'm > running 3.0 on our [production] server...", very scary ;-) This is NOT the case. I was referring to normal development work on -current. People complain about not having better thread support. People complain about developers not testing things before committing them. Well if the committers themselves can't run -current, what do they do? Commit anyway? Delay commits for a month? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message