From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Wed, 15 Sep 2010 14:16:04 +0200 Subject: [U-Boot] [PATCH] [NEXT] arm926ejs: add split relocation support In-Reply-To: <20100915065944.B6BC015242D@gemini.denx.de> References: <1284488741-16899-1-git-send-email-albert.aribaud@free.fr> <4C8FC35B.9050902@free.fr> <4C8FDAF0.4090709@dawes.za.net> <4C905F6D.7010902@free.fr> <20100915065944.B6BC015242D@gemini.denx.de> Message-ID: <4C90B904.9020305@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Le 15/09/2010 08:59, Wolfgang Denk a ?crit : > Dear Albert ARIBAUD, > > In message<4C905F6D.7010902@free.fr> you wrote: >> >> Both encodings are present in u-boot. I figure UTF-8 seems a better >> choice, but if there is a coding rule about encodings, I'll happily >> follow it, of course. > > So far we've been using ISO8859-1 It is not clear to me whether you're expressing a coding rule or just a statement of fact, so I'll ask more precise questions: 1) is UTF-8 allowed or not in u-boot? 2) if UTF-8 is allowed along with ISO8859-1, then a) which one should be preferred for new files, and b) which should be preferred for patches to existing files? 3) if UTF-8 is not allowed, then what should be done about the 56 u-boot source files that currently are UTF-8? Wolfgang, can you explicitly answer these points? In case the answer to question 3 is "they should be converted to ISO", of course being the one to raise the issue, I shall be the one to submit the fix. Amicalement, -- Albert.