From owner-freebsd-gecko@FreeBSD.ORG Tue Dec 27 12:38:50 2011 Return-Path: Delivered-To: gecko@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F7FA1065672 for ; Tue, 27 Dec 2011 12:38:50 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 158F08FC12 for ; Tue, 27 Dec 2011 12:38:49 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 27 Dec 2011 07:38:49 -0500 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id BMP34335; Tue, 27 Dec 2011 07:38:48 -0500 X-Auth-ID: anat Received: from 209-6-61-133.c3-0.sbo-ubr1.sbo.ma.cable.rcn.com (HELO [192.168.1.8]) ([209.6.61.133]) by smtp04.lnh.mail.rcn.net with ESMTP; 27 Dec 2011 07:38:48 -0500 Message-ID: <4EF9BC57.8050605@aldan.algebra.com> Date: Tue, 27 Dec 2011 07:38:47 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.2) Gecko/20110926 Thunderbird/6.0.2 MIME-Version: 1.0 To: Florian Smeets References: <4EF7C66F.9090005@aldan.algebra.com> <4EF81D1C.3090405@FreeBSD.org> In-Reply-To: <4EF81D1C.3090405@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: gecko@FreeBSD.org Subject: Re: New nss and firefox X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 12:38:50 -0000 On 26.12.2011 02:07, Florian Smeets wrote: > replying only to the nss part of you email. We have nss 3.13.1 in our > svn tree (not the with CKBI 1.88 version yet, I'll get to it) and we > decided to wait with updating the version in ports until after FreeBSD > 9.0-RELEASE. Is there a ports-freeze in effect? If not, why can't nss be updated now? -mi