Date: Sun, 19 Aug 2012 18:36:56 -0700 (PDT)
From: Karl Tiedt <kti...@gmail.com>
To: node-webkit@googlegroups.com
Message-Id: <2cd3f36a-6a6e-4b5d-b41f-70e6fc84d72a@googlegroups.com>
In-Reply-To: <CAABYkTPcjtxmo9LWV3JSmZHKi_Qy5R4c8KSzrS5UHJLzvommSg@mail.gmail.com>
References: <CAABYkTPcjtxmo9LWV3JSmZHKi_Qy5R4c8KSzrS5UHJLzvommSg@mail.gmail.com>
Subject: Re: New version of node-webkit is released
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_348_15192001.1345426616862"

------=_Part_348_15192001.1345426616862
Content-Type: multipart/alternative; 
	boundary="----=_Part_349_16292827.1345426616862"

------=_Part_349_16292827.1345426616862
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

How often do the binaries get updated? It seems *every* fix I needed was 
checked in just after this last release announcement... I just tested to 
confirm they were still not addressed in the current binaries.



------=_Part_349_16292827.1345426616862
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

How often do the binaries get updated? It seems *every* fix I needed was checked in just after this last release announcement... I just tested to confirm they were still not addressed in the current binaries.<div><br><br></div>
------=_Part_349_16292827.1345426616862--

------=_Part_348_15192001.1345426616862--