From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rene Herman Subject: Re: [PATCH -mm] sb16: Shut up uninitialized var build warning Date: Sat, 22 Sep 2007 06:20:00 +0200 Message-ID: <46F497F0.1090608@gmail.com> References: <46DB33D0.40204@gmail.com> <200709201852.11497.vda.linux@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtpq2.groni1.gr.home.nl (smtpq2.groni1.gr.home.nl [213.51.130.201]) by alsa0.perex.cz (Postfix) with ESMTP id B6E2A246F6 for ; Sat, 22 Sep 2007 06:21:27 +0200 (CEST) In-Reply-To: <200709201852.11497.vda.linux@googlemail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Denys Vlasenko Cc: Takashi Iwai , alsa-devel@alsa-project.org, Linux Kernel Mailing List , Jaroslav Kysela , Satyam Sharma List-Id: alsa-devel@alsa-project.org On 09/20/2007 07:52 PM, Denys Vlasenko wrote: > On Sunday 02 September 2007 23:06, Rene Herman wrote: >> Blah. Your message has: >> >> Content-Type: TEXT/PLAIN; charset=iso-2022-jp >> >> This apparently is caused by a combination of GCC using groovy UTF tickmarks >> in its error messages when in a UTF locale and alpine believing it to be a >> great idea to automatically try for the "simplest" character set it can >> encode the content in. No idea why that means that iso-2022-jp is picked, >> but it is. >> >> While I could actually read the message this time you should see what >> iso-2022-jp does to my font. It's scary. Best solution as far as I'm >> concerned is slap a few GCC developers (not that it wil help, but it'll >> certainly feel good) and then teach alpine to go for UTF-8 directly if >> US-ASCII won't do. > > rotfl. > > Kindly give me permission to convert your email into gcc bugreport > and/or to forward it to gcc mailing list. Blessings be upon thou, oh courageous one... Rene. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755552AbXIVEVc (ORCPT ); Sat, 22 Sep 2007 00:21:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751546AbXIVEVZ (ORCPT ); Sat, 22 Sep 2007 00:21:25 -0400 Received: from smtpq2.groni1.gr.home.nl ([213.51.130.201]:49264 "EHLO smtpq2.groni1.gr.home.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751309AbXIVEVY (ORCPT ); Sat, 22 Sep 2007 00:21:24 -0400 Message-ID: <46F497F0.1090608@gmail.com> Date: Sat, 22 Sep 2007 06:20:00 +0200 From: Rene Herman User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Denys Vlasenko CC: Satyam Sharma , Linux Kernel Mailing List , Takashi Iwai , Jaroslav Kysela , alsa-devel@alsa-project.org Subject: Re: [PATCH -mm] sb16: Shut up uninitialized var build warning References: <46DB33D0.40204@gmail.com> <200709201852.11497.vda.linux@googlemail.com> In-Reply-To: <200709201852.11497.vda.linux@googlemail.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 09/20/2007 07:52 PM, Denys Vlasenko wrote: > On Sunday 02 September 2007 23:06, Rene Herman wrote: >> Blah. Your message has: >> >> Content-Type: TEXT/PLAIN; charset=iso-2022-jp >> >> This apparently is caused by a combination of GCC using groovy UTF tickmarks >> in its error messages when in a UTF locale and alpine believing it to be a >> great idea to automatically try for the "simplest" character set it can >> encode the content in. No idea why that means that iso-2022-jp is picked, >> but it is. >> >> While I could actually read the message this time you should see what >> iso-2022-jp does to my font. It's scary. Best solution as far as I'm >> concerned is slap a few GCC developers (not that it wil help, but it'll >> certainly feel good) and then teach alpine to go for UTF-8 directly if >> US-ASCII won't do. > > rotfl. > > Kindly give me permission to convert your email into gcc bugreport > and/or to forward it to gcc mailing list. Blessings be upon thou, oh courageous one... Rene.