From: Adrian Bunk <bunk@stusta.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jcm@jonmasters.org, Jan Engelhardt <jengelh@computergmbh.de>,
Andy Whitcroft <apw@shadowen.org>, Andrew Morton <akpm@osdl.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Joel Schopp <jschopp@austin.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update checkpatch.pl to version 0.03
Date: Fri, 8 Jun 2007 16:42:31 +0200 [thread overview]
Message-ID: <20070608144230.GA5500@stusta.de> (raw)
In-Reply-To: <9a8748490706080734h6ce5959fq6e7cb802d9a555cc@mail.gmail.com>
On Fri, Jun 08, 2007 at 04:34:01PM +0200, Jesper Juhl wrote:
> On 08/06/07, Adrian Bunk <bunk@stusta.de> wrote:
> [snip]
>>
>> It's not only about MODULE_AUTHOR, if you consider it rude to limit
>> people's names to ASCII, then don't forget that we have printk's like
>> Linux agpgart interface v0.102 (c) Dave Jones
>>
>> What happens if the maintainer changes and it's now
>> Linux agpgart interface v0.103 (c) Dave Ønes
>>
>> Does the console handle it correctly during boot?
>> Can all tools that process the syslog cope with it?
>>
>> Perhaps the answer is in both cases "yes", but it's a completely
>> untested area.
>>
>> We really must have all bugs shaken out and all users using fixed tools
>> _before_ we can start outputting UTF-8 - limiting people's names to
>> ASCII in not ideal, but IMHO causing breakages for users is a much
>> bigger problem.
>
> I haven't looked at it in depth yet, but it would seem we already have
> a few files that need to be looked at with this in mind. Looks like
> it's not exactely a new problem (although all the following could be
> in comments of course)...
>...
They should all be in comments, and all UTF-8 I've ever seen in such
files was only in comments (mostly author names). So yes, adding UTF-8
to program code will result in new problems.
If you find any source file that contains UTF-8 outside of comments
please complain loudly.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-06-08 14:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 9:46 [PATCH] update checkpatch.pl to version 0.03 Andy Whitcroft
2007-06-04 9:55 ` [PATCH] update feature-removal-schedule.txt to include deprecated functions Andy Whitcroft
2007-06-04 15:49 ` [PATCH] update checkpatch.pl to version 0.03 jschopp
2007-06-04 16:51 ` Andy Whitcroft
2007-06-04 17:22 ` jschopp
2007-06-05 18:45 ` Andy Whitcroft
2007-06-05 9:56 ` Andy Whitcroft
2007-06-04 16:25 ` Jan Engelhardt
2007-06-04 18:41 ` Andrew Morton
2007-06-04 19:08 ` Andy Whitcroft
2007-06-04 19:08 ` Rene Herman
2007-06-04 20:04 ` Randy Dunlap
2007-06-05 18:39 ` Andy Whitcroft
2007-06-08 9:31 ` Andy Whitcroft
2007-06-08 10:08 ` Rene Herman
2007-06-05 8:14 ` Heiko Carstens
2007-06-06 9:05 ` Jesper Juhl
2007-06-07 14:28 ` Jan Engelhardt
2007-06-07 14:39 ` Jesper Juhl
2007-06-07 19:34 ` Adrian Bunk
2007-06-07 22:22 ` Alan Cox
2007-06-07 23:21 ` Adrian Bunk
2007-06-07 23:41 ` Alan Cox
2007-06-08 0:04 ` Adrian Bunk
2007-06-08 4:37 ` Jon Masters
2007-06-08 8:58 ` Jan-Benedict Glaw
2007-06-08 10:52 ` Alan Cox
2007-06-08 12:39 ` Adrian Bunk
2007-06-08 14:34 ` Jesper Juhl
2007-06-08 14:42 ` Adrian Bunk [this message]
2007-06-08 15:16 ` Jan Engelhardt
2007-06-08 15:37 ` Jon Masters
2007-06-08 15:42 ` Alan Cox
2007-06-08 16:39 ` Adrian Bunk
2007-06-08 18:43 ` Jan Engelhardt
2007-06-08 16:03 ` Roland Dreier
2007-06-07 23:49 ` Adrian Bunk
2007-06-07 19:32 ` Adrian Bunk
2007-06-07 22:18 ` Alan Cox
2007-06-06 11:49 ` Jesper Juhl
2007-06-07 11:46 ` Andy Whitcroft
2007-06-07 11:52 ` Jesper Juhl
2007-06-07 15:16 ` checkpatch.pl: should be executable Andy Whitcroft
2007-06-07 15:33 ` jschopp
2007-06-07 14:22 ` [PATCH] update checkpatch.pl to version 0.03 Jan Engelhardt
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=20070608144230.GA5500@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=apw@shadowen.org \
--cc=jcm@jonmasters.org \
--cc=jengelh@computergmbh.de \
--cc=jesper.juhl@gmail.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.