Date: Wed, 21 Jun 2000 09:22:02 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Jason Evans <jasone@canonware.com> Cc: Warner Losh <imp@village.org>, The Hermit Hacker <scrappy@hub.org>, freebsd-smp@FreeBSD.ORG Subject: Re: SMP discussion moving to freebsd-smp Message-ID: <58201.961572122@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 21 Jun 2000 00:10:50 PDT." <20000621001050.E233@blitz.canonware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20000621001050.E233@blitz.canonware.com>, Jason Evans writes: >This is in my opinion a bit revisionist, but part of the blame falls on me >for not clarifying "destabilization" adequately. -current will continue to >compile for the most part, and may even work okay most of the time. I think it is this "may" that people are not comfortable with. It sounds like "Hey, it's broken but - what me worry ?" rather than "It's broken we know, we're doing our best to fix it." If we had heard you say "Unfortunately this will mean that -current will be broken at times, but we will do what we can to minimize this so we don't impact the rest of the FreeBSD developers more than absolutely necessary." I'm sure people would not be up in arms the way they are. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58201.961572122>