From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/3] at91rm9200ek: convert to at91
Date: Tue, 19 Oct 2010 09:29:10 +0200 [thread overview]
Message-ID: <4CBD48C6.2060307@gmail.com> (raw)
In-Reply-To: <4CBCBE26.3070102@emk-elektronik.de>
Dear Reinhard Meyer,
Am 18.10.2010 23:37, schrieb Reinhard Meyer:
> Dear Andreas Bie?mann,
>> Signed-off-by: Andreas Bie?mann<andreas.devel@googlemail.com>
This is correct UTF8 coded line
>> +Andreas Bie?mann<andreas.devel@gmail.com>
This is a patch to a latin1 coded file. When you e.g. save this mail and
look through it with 'cat <file> | less' you may see 'Andreas
Bie<DF>mann <andreas.devel@gmail.com>'.
When you then look for latin1 coding table you may see <DF> is '?'. So
this is correct here. Some other files in the patch are still coded in
utf-8 (as the mail is), therefore your MUA represents the stuff correct
to you.
The file MAINTAINERS is in latin1 coding cause a lot of/some other
contributors also have non-ASCII characters in their names. A short test
will show this to you:
open MAINTAINERS in vim; :set fileencoding=utf8; save; git diff
> in the 2nd line the "?" does not show here (a "FFFD" box is shown
> instead. Is it only me or
> do others have similar problems?
No, everyone with correct configured MUA should see this
> I think that line was produced
> in a different code page?
Yes, the file MAINTAINERS is in latin1 while the mail and some other
files touched are in utf-8.
> Maybe we should refrain from using non
> ASCII characters within source code?
I don't know. But my surname is Bie?mann and _not_ Biessmann.
Shouldn't we change the coding for all files to utf-8 instead?
regards
Andreas Bie?mann
next prev parent reply other threads:[~2010-10-19 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 0:41 [U-Boot] [PATCH 0/3] new BSP for at91rm9200ek Andreas Bießmann
2010-10-16 0:41 ` [U-Boot] [PATCH 1/3] at91rm9200ek: convert to at91 Andreas Bießmann
2010-10-17 18:06 ` Reinhard Meyer
2010-10-17 18:40 ` Wolfgang Denk
2010-10-18 6:36 ` Andreas Bießmann
2010-10-18 6:46 ` Wolfgang Denk
2010-10-18 6:36 ` Andreas Bießmann
2010-10-18 8:40 ` Reinhard Meyer
2010-10-18 9:27 ` Andreas Bießmann
2010-10-18 11:21 ` Reinhard Meyer
2010-10-16 0:41 ` [U-Boot] [PATCH 2/3] at91rm9200: enable USB support Andreas Bießmann
2010-10-16 0:41 ` [U-Boot] [PATCH 3/3] at91rm9200ek: enbable " Andreas Bießmann
2010-10-18 20:58 ` [U-Boot] [PATCH v2 1/3] at91rm9200ek: convert to at91 Andreas Bießmann
2010-10-18 20:58 ` [U-Boot] [PATCH v2 2/3] at91rm9200: enable USB support Andreas Bießmann
2010-10-18 20:58 ` [U-Boot] [PATCH v2 3/3] at91rm9200ek: enbable " Andreas Bießmann
2010-10-18 21:37 ` [U-Boot] [PATCH v2 1/3] at91rm9200ek: convert to at91 Reinhard Meyer
2010-10-19 7:29 ` Andreas Bießmann [this message]
2010-10-19 13:52 ` [U-Boot] [PATCH 0/3] new BSP for at91rm9200ek Reinhard Meyer
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=4CBD48C6.2060307@gmail.com \
--to=andreas.devel@googlemail.com \
--cc=u-boot@lists.denx.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