Message from discussion
Fx10.0.9 ESR when available?
Received: by 10.66.73.1 with SMTP id h1mr1686859pav.0.1350121580046;
Sat, 13 Oct 2012 02:46:20 -0700 (PDT)
MIME-Version: 1.0
Path: s9ni5139pbb.0!nntp.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail
NNTP-Posting-Date: Sat, 13 Oct 2012 04:46:19 -0500
From: "Desiree" <melel...@medscape.com>
Newsgroups: mozilla.support.firefox
References: <qOqdnczz-Pwmd-rNnZ2dnUVZ_h2dnZ2d@mozilla.org> <y6WdnaPC47caxOXNnZ2dnUVZ_qydnZ2d@mozilla.org>
Subject: Re: Fx10.0.9 ESR when available?
Date: Fri, 12 Oct 2012 23:46:19 -1000
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3664
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
Message-ID: <FvSdnVEaAun2peTNnZ2dnUVZ_v6dnZ2d@mozilla.org>
Lines: 20
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 76.93.196.111
X-AuthenticatedUsername: NoAuthUser
X-Trace: sv3-WIH74mf8LC20z8V7WvwxKo3xIlgcjMsn5hJHPscNUdY2t5GbkVuaBsZdnTQxovnJOHkM4HME+pp2J47!R8SuAgBFEgD3xA+Tg1HQQ4aBkdnz7oBCLcbQbAVziSIX+WknObL4eFMRuMvkbow9MCTiqQWKm/7L!bvtcV6a8eZKQ
X-Complaints-To: abuse@mozilla.org
X-DMCA-Complaints-To: ab...@mozilla.org
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
Bytes: 1952
X-Original-Bytes: 1891
"Chris Ilias" <n...@ilias.ca> wrote in message
news:y6WdnaPC47caxOXNnZ2dnUVZ_qydnZ2d@mozilla.org...
> On 12-10-12 6:02 AM, Desiree wrote:
>> When will Fx 10.0.9 ESR be available via internal update? Is it available
>> now by another method?
>
> It was pushed to the ESR channel 3 hours ago (around 5 hours after your
> post).
>
> --
> Chris Ilias <http://ilias.ca>
> Mailing list/Newsgroup moderator
I got it this evening. It was bit odd as it abruptly killed the Guy with no
warning (process still running in Task Manager) and then took much longer
than usual to start back up. But everything was fine when it did start up
again.