From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 20 13:59:39 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EE73106564A for ; Fri, 20 Jan 2012 13:59:39 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id EA4018FC0A for ; Fri, 20 Jan 2012 13:59:38 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id q0KDxbJd017423; Fri, 20 Jan 2012 17:59:37 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id q0KDxawT017422; Fri, 20 Jan 2012 17:59:36 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 20 Jan 2012 17:59:36 +0400 From: Gleb Smirnoff To: Damien Fleuriot Message-ID: <20120120135936.GC16676@FreeBSD.org> References: <4F153AE3.9010602@my.gd> <20120120133826.GB16676@FreeBSD.org> <4F196F9B.3050506@my.gd> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4F196F9B.3050506@my.gd> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-hackers@FreeBSD.org Subject: Re: FreeBSD has serious problems with focus, longevity, and lifecycle X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 13:59:39 -0000 On Fri, Jan 20, 2012 at 02:43:55PM +0100, Damien Fleuriot wrote: D> Don't be mistaken, I greatly appreciate the work you put into this and D> the time you devoted to fixing this issue which was *a real annoyance* D> in our case. D> D> I'm not saying you didn't merge it Gleb, I'm saying for a loooooooong D> time I had to manually patch the 8.2-RELEASE boxes, because for some D> reason that I don't know/understand, the patch couldn't (and still D> hasn't been, I guess) be merged with 8.2-RELEASE. D> D> Actually, on topic, what prevents patches from being merged with D> -RELEASE, as opposed to waiting for a new -RELEASE bump ? It cannot be merged into RELEASE! RELEASE is a point on a branch, as soon as RELEASE had been released, you can't push anything into it, unless you have a time machine. So, the fix has been merged to the branch you reported problem on, this means that it'll be available in the next release from this branch - in 8.3-RELEASE. -- Totus tuus, Glebius.