From owner-freebsd-stable@FreeBSD.ORG Thu Jun 5 15:39:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36ACD106566B for ; Thu, 5 Jun 2008 15:39:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id 0506C8FC16 for ; Thu, 5 Jun 2008 15:39:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so810584rvf.43 for ; Thu, 05 Jun 2008 08:39:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=g8sHzkZMVVm6iTWUA6EUtRooldgifa31/5Mj43W7pk0=; b=Ea7r4CxxrveesghtPOj8hy/oDmFtcMfcdpOS/zdoDrR1zRZhl+ufUcR0bXVEKd4adt xbVCnRSdhhguXTPkpKBQFrBRqdTTLfifF+EhhnPJPLOVpB8NzeuW4UV/9qNUM/LKj3t/ SL3Tb0qF5punNEJAoA3/0SIZ3pnY9ytOBi3Ic= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=c9k2J5irWNzzBeEh7ekOLmf7Xx7jERaZoZJNOKPKd3mtf2FQhEcQiwgIv98iEWlaHo GGiWKxp3/hhkYS4hPn10q8bdJS3uP9fpsoShulzHBP4qGtrWR4BwNbR9c8vJCJMhNv59 9cX//3Yyrm+loRTJijMRhhRI54Xq0zLNSkdkk= Received: by 10.141.163.12 with SMTP id q12mr954367rvo.265.1212680357810; Thu, 05 Jun 2008 08:39:17 -0700 (PDT) Received: by 10.141.70.11 with HTTP; Thu, 5 Jun 2008 08:39:17 -0700 (PDT) Message-ID: Date: Thu, 5 Jun 2008 23:39:17 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Chris Marlatt" In-Reply-To: <4848073C.2060509@rxsec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <4846E14C.709@FreeBSD.org> <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4848073C.2060509@rxsec.com> X-Google-Sender-Auth: 0f837fec0fb76cab Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2008 15:39:18 -0000 (I know I should really be studying, but this thread really irks me, as I have exactly this issue in the project _I_ am involved in..) 2008/6/5 Chris Marlatt : > Again IMHO the only message coming across here is either do it yourself or > keep your mouth shut. The other side of the coin here is - what's to say the Well, its "do it yourself or be helpful to people who are willing to do it". The OP stated "argh argh sky is falling with 6.3!" but hasn't yet listed PRs which indicate this to be happening. He's offered hardware in a week or two - which is great! - but what irks the developers is the large amount of noise and absolutely no useful information. Anyone can say "its broken!".. > FreeBSD project requires what I can offer? Granted it's been sometime since > I've browsed the entire FreeBSD.org site but last I checked there wasn't an > area devoted to the needs of the project. Whatever you want..? > Furthermore, just because someone isn't providing assistance doesn't mean > that their concerns should go unheard. It's quite possible what was proposed > is an awful idea and if it is so be it. But it would appear as though it > wasn't even considered. Thats true in say, your case. And, say another case like yours. But after hundreds of people who aren't providing assistance and are simply providing their 2c, it gets a bit tiresome. Its not that ALL of the comments aren't any good, its that wading through the crap to find the gems is more effort than fun, and people have real work to do! So yes, the way to contribute is to get involved. If you think there's a real desire to take FreeBSD-6.2 (as an example) and continue supporting security patches and critical bugfixes, versus the larger-scale changes which seem to have gone on in /usr/src/sys then just get together a group, generate some patches and submit them. At some point the poor sod who is committing your work will say "screw this, he's getting a commit bit".. Adrian -- Adrian Chadd - adrian@freebsd.org