From owner-freebsd-gecko@FreeBSD.ORG Tue Jul 23 11:43:21 2013 Return-Path: Delivered-To: gecko@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E222CE02 for ; Tue, 23 Jul 2013 11:43:21 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp.rcn.com (smtp.rcn.com [69.168.97.78]) by mx1.freebsd.org (Postfix) with ESMTP id AF8DB2984 for ; Tue, 23 Jul 2013 11:43:21 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=2.1 cv=G7glTbU5 c=1 sm=0 tr=0 a=nVny9ETX7T5uMhI2oTVyRA==:117 a=nVny9ETX7T5uMhI2oTVyRA==:17 a=K-v-2zaBAAAA:8 a=AaUjGI9IrlcA:10 a=kj9zAlcOel0A:10 a=OA2lqS22AAAA:8 a=sIt-5M63AAAA:8 a=qEzWG9Z-EVcA:10 a=8rnLHB6AoI82VTWeck0A:9 a=CjuIK1q_8ugA:10 a=HBS41oGvtocA:10 a=vF9sAn3mQYwA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp01.rcn.cmh.synacor.com header.from=roberthuff@rcn.com; sender-id=neutral Authentication-Results: smtp01.rcn.cmh.synacor.com smtp.mail=roberthuff@rcn.com; spf=neutral; sender-id=neutral Received-SPF: neutral (smtp01.rcn.cmh.synacor.com: 209.6.193.164 is neither permitted nor denied by domain of rcn.com) Received: from [209.6.193.164] ([209.6.193.164:23803] helo=jerusalem.litteratus.org.litteratus.org) by smtp.rcn.com (envelope-from ) (ecelerity 2.2.3.49 r(42060/42061)) with ESMTP id E3/55-21927-25C6EE15; Tue, 23 Jul 2013 07:43:15 -0400 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20974.27730.438838.702055@jerusalem.litteratus.org> Date: Tue, 23 Jul 2013 07:43:14 -0400 To: gecko@freebsd.org Subject: seamonkey-2.19 fixed? X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2013 11:43:21 -0000 Hello: The bug referenced in the BROKEN message appears to have been fixed about a week ago. So ... is the port still broken? Respectfully, Robert Huff