On 19 November 2012 07:20, Brendan Jones wrote:
> On 11/17/2012 09:42 AM, Ian Malone wrote:
>>
>> On 17 November 2012 03:09, Orcan Ogetbil wrote:
>>>
>>> On Fri, Nov 16, 2012 at 5:24 PM, Ian Malone wrote:
On 15 November 2012 23:20, Ian Malone wrote:
>
> On 15 November 2012 04:
On 11/17/2012 09:42 AM, Ian Malone wrote:
On 17 November 2012 03:09, Orcan Ogetbil wrote:
On Fri, Nov 16, 2012 at 5:24 PM, Ian Malone wrote:
On 15 November 2012 23:20, Ian Malone wrote:
On 15 November 2012 04:40, Orcan Ogetbil wrote:
Hi all,
A few months ago earlier in the F-17 release c
On 17 November 2012 03:09, Orcan Ogetbil wrote:
> On Fri, Nov 16, 2012 at 5:24 PM, Ian Malone wrote:
>> On 15 November 2012 23:20, Ian Malone wrote:
>>> On 15 November 2012 04:40, Orcan Ogetbil wrote:
Hi all,
A few months ago earlier in the F-17 release cycle, we had a problem
>>
On Fri, Nov 16, 2012 at 5:24 PM, Ian Malone wrote:
> On 15 November 2012 23:20, Ian Malone wrote:
>> On 15 November 2012 04:40, Orcan Ogetbil wrote:
>>> Hi all,
>>>
>>> A few months ago earlier in the F-17 release cycle, we had a problem
>>> with jackd turning verbose, flooding the stdout, even
On 15 November 2012 23:20, Ian Malone wrote:
> On 15 November 2012 04:40, Orcan Ogetbil wrote:
>> Hi all,
>>
>> A few months ago earlier in the F-17 release cycle, we had a problem
>> with jackd turning verbose, flooding the stdout, even when its
>> verbosity was turned off. This was a bug [1] in
On 15 November 2012 04:40, Orcan Ogetbil wrote:
> Hi all,
>
> A few months ago earlier in the F-17 release cycle, we had a problem
> with jackd turning verbose, flooding the stdout, even when its
> verbosity was turned off. This was a bug [1] in the compiler,
> specifically in the optimized builds
