public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-arm/master (updated)
Date: Fri, 01 Jul 2011 12:55:48 +0200	[thread overview]
Message-ID: <4E0DA7B4.8050209@gmail.com> (raw)
In-Reply-To: <4E0D9BFE.9080507@emk-elektronik.de>

Dear Reinhard Meyer,

Am 01.07.2011 12:05, schrieb Reinhard Meyer:
> Dear All,
>> Le 01/07/2011 08:22, Andreas Bie?mann a ?crit :
>>> Dear all,
>>>
>>> Am 30.06.2011 um 13:16 schrieb Albert ARIBAUD:
>>>
>>> <snip>
>>>
>>>> Andreas Bie?mann (1):
>>>>        atstk100x: switch to common cfi driver
> 
> Patchwork says: Signed-off-by: Andreas Bie?mann <andreas.devel@googlemail.com>
> 
> Saved mbix file starts like:
> 
> From patchwork Tue Jun 28 14:15:58 2011
> Content-Type: text/plain; charset="utf-8"

<snip>

> Signed-off-by: Andreas Bie??mann <biessmann@corscience.de>

<snip>

> 
> Patchworks says: Signed-off-by: Andreas Bie?mann <biessmann@corscience.de>
> 
> Saved mbox file starts like:
> 
> From patchwork Sun Jun 12 11:49:13 2011
> Content-Type: text/plain; charset="utf-8"

<snip>

> Signed-off-by: Andreas Bie??mann <andreas.devel@googlemail.com>

>> Reinhard, what commands did you use to applie these patches?
> 
> ALWAYS using patchworks: Download mbox, git-am <the downloaded file>.
> 
> Apparently it makes a difference where the mail originated from.

Well, if I load the two patchwork ID's 100078 and 102387 both patches
are correctly UTF-8 coded. In your mail the '??' is due to wrong
conversion on your box -> (charset=windows-1252 == ISO-8859-1 but the
mail contains the correctly UTF-8 coded char '?')

try the following:
---8<---
echo -e '\xc3\x9f\x0a' | iconv -f ISO-8859-1 -t UTF-8
echo ? | iconv -f ISO-8859-1 -t UTF-8
--->8---

It should show the same two chars '??' (if your shell environment is set
to UTF-8) ...

I guess it has something to do with wrong shell environment
settings/misconfigured git/ ... but indeed it is something on your side
Reinhard.

I do not insist on modified commits, therefore it could be pulled in
mainline. But for the future, Reinhard please check your environment.

regards

Andreas Bie?mann

  parent reply	other threads:[~2011-07-01 10:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 11:16 [U-Boot] Pull request: u-boot-arm/master (updated) Albert ARIBAUD
2011-07-01  6:22 ` Andreas Bießmann
2011-07-01  6:44   ` Albert ARIBAUD
2011-07-01 10:05     ` Reinhard Meyer
2011-07-01 10:47       ` Reinhard Meyer
2011-07-01 11:02         ` Andreas Bießmann
2011-07-01 11:07           ` Reinhard Meyer
2011-07-01 11:14             ` Andreas Bießmann
2011-07-01 11:45               ` Andreas Bießmann
2011-07-01 11:47               ` Reinhard Meyer
2011-07-01 11:49                 ` Andreas Bießmann
2011-07-02  8:18                 ` Albert ARIBAUD
2011-07-01 10:55       ` Andreas Bießmann [this message]
2011-07-01 11:04         ` Albert ARIBAUD
2011-07-01 10:59       ` Albert ARIBAUD
2011-07-01 11:04         ` Reinhard Meyer
2011-07-03 20:04   ` Albert ARIBAUD
2011-07-03 20:23     ` Andreas Bießmann
2011-07-03 20:46       ` Albert ARIBAUD

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=4E0DA7B4.8050209@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