From owner-freebsd-stable Sat Nov 27 9:37:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 63A8314BDA for ; Sat, 27 Nov 1999 09:37:37 -0800 (PST) (envelope-from cwass99@home.com) Received: from home.com ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991127173538.PREW6014.mail.rdc3.on.home.com@home.com>; Sat, 27 Nov 1999 09:35:38 -0800 Message-ID: <3840165D.CAF495E9@home.com> Date: Sat, 27 Nov 1999 12:35:25 -0500 From: Colin X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: "Forrest W. Christian" Cc: Stable@freebsd.org Subject: Re: Bug-fixing previous -RELEASE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forrest W. Christian wrote: > > Hmm, this brings up another interesting question. First, to put this in > context: > > Jordan K. Hubbard wrote: > > Actually, the -missioncritical branch is sort of provided for > > now as a function of -previousstable. There are plenty of people still > > running 2.2.x, for example, and you even still occasionally see commits > > to the 2.2.x branch. > > Ok, so, let's assume I JUST want to incorporate bugfixes into the -RELEASE > (be it 3.x or whatever) that I have on a particular machine. How would I > go about doing this? > My intent was actually a little different from the responses that are elswhere in this list. My thought was, when you find a bug that affects you, get the diffs/upgraded source that fixes that problem only and apply. I'm new enough to this branch that I don't know for sure how difficult that would be, but I don't imagine it would be that big of a deal. You could also move just far enough up the source tree to fix your current problems and stop there, but at that point, there's no more risk than tracking -STABLE completely. For systems where stability is the overriding concern, you never want to apply patches/fixes only because they are available. Only fix problems that actually have an impact i.e. if SSH is broken, but you don't use it, don't worry about fixing it. There's always a risk that code that fixes one problem will break something else, usually something important ;) Murphy's Law always takes care of the final QA ;) Cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message