From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Andrew Pinski <pinskia@gcc.gnu.org>, <overseers@sourceware.org>
Subject: Re: gcc.gnu.org/sourceware.org SSL issues?
Date: Tue, 02 Sep 2014 14:34:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1409021526560.2958@tp.orcam.me.uk> (raw)
In-Reply-To: <alpine.LSU.2.11.1409020838430.5181@tuna.site>
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
next prev parent reply other threads:[~2014-09-02 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 2:47 Maciej W. Rozycki
2014-09-02 2:49 ` Andrew Pinski
2014-09-02 3:23 ` Maciej W. Rozycki
2014-09-02 6:40 ` Gerald Pfeifer
2014-09-02 14:34 ` Maciej W. Rozycki [this message]
2014-09-02 4:45 ` Hans-Peter Nilsson
2014-09-02 18:18 ` Maciej W. Rozycki
2014-09-02 14:52 ` Joseph S. Myers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.1409021526560.2958@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=gerald@pfeifer.com \
--cc=overseers@sourceware.org \
--cc=pinskia@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).