From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18506 invoked by alias); 2 Sep 2014 14:34:03 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 18484 invoked by uid 89); 2 Sep 2014 14:34:02 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 02 Sep 2014 14:34:01 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-FEM-01.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1XOp9e-0006xK-C6 from Maciej_Rozycki@mentor.com ; Tue, 02 Sep 2014 07:33:55 -0700 Received: from localhost (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server (TLS) id 14.2.247.3; Tue, 2 Sep 2014 15:33:53 +0100 Date: Tue, 02 Sep 2014 14:34:00 -0000 From: "Maciej W. Rozycki" To: Gerald Pfeifer CC: Andrew Pinski , Subject: Re: gcc.gnu.org/sourceware.org SSL issues? In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2014-q3/txt/msg00124.txt.bz2 On Tue, 2 Sep 2014, Gerald Pfeifer wrote: > > I switch between two versions of Firefox (or Iceape/Iceweasel which is > > how Debian prefers to call it): `Iceape 1.0.9' is my usual choice and for > > sites that are picky/weird I use `Firefox 3.5.19', both according to > > Help->About. > > Firefox 3.6 was released early in 2010, four-and-a-half years ago; > is using a current version (not) an option? As far as rebuilding from sources -- it certainly is. Question is: can I afford it? I keep using 1.0.9 as my default browser, it's just got the right pieces in the right places, unlike any later versions. Why do people writing this software think along bug fixes and engine updates they absolutely must change the UI as well? Anyway the warning has disappeared with 3.5.19 now and things work past that point, so I think I'm set, at least till the next issue, that is. ;) Thanks, Maciej