From: Denys Vlasenko <vda.linux@googlemail.com>
To: Rene Herman <rene.herman@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jaroslav Kysela <perex@suse.cz>,
Satyam Sharma <satyam@infradead.org>
Subject: Re: [PATCH -mm] sb16: Shut up uninitialized var build warning
Date: Thu, 20 Sep 2007 18:52:11 +0100 [thread overview]
Message-ID: <200709201852.11497.vda.linux@googlemail.com> (raw)
In-Reply-To: <46DB33D0.40204@gmail.com>
On Sunday 02 September 2007 23:06, Rene Herman wrote:
> On 09/02/2007 10:15 PM, Satyam Sharma wrote:
>
> > sound/isa/sb16/sb16.c: In function ‘snd_sb16_isa_probe’:
>
> 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.
--
vda
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2007-09-20 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.999.0709022344550.27844@enigma.security.iitk.ac.i n>
[not found] ` <alpine.LFD.0.999.0709022344550.27844@enigma.security.iitk.ac.in>
2007-09-02 20:15 ` [PATCH -mm] sb16: Shut up uninitialized var build warning Satyam Sharma
2007-09-02 22:06 ` Rene Herman
2007-09-02 22:34 ` Satyam Sharma
2007-09-20 17:52 ` Denys Vlasenko [this message]
2007-09-22 4:20 ` Rene Herman
2007-09-02 20:21 ` [PATCH -mm] es18xx: " Satyam Sharma
2007-09-02 22:14 ` Rene Herman
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=200709201852.11497.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=rene.herman@gmail.com \
--cc=satyam@infradead.org \
--cc=tiwai@suse.de \
/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