All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Danis <frederic.danis@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] fix build
Date: Mon, 17 Oct 2011 17:59:27 +0200	[thread overview]
Message-ID: <4E9C50DF.5020703@linux.intel.com> (raw)
In-Reply-To: <4E9C27BE.10006@linux.intel.com>

Hello Johan,

>>
>> I'd push the patch upstream but it fails to apply:
>>
>> fatal: cannot convert from UTF-8utf-8 to UTF-8
>>
>> I suspect that's because of the double Content-Type header in your
>> email. Could you try to fix it?
>
> I will send new version removing double Content-Type header

I finally found that ‘ generates this behavior, replacing it by ' remove 
the "cannot convert from UTF-8utf-8" problem.

Sent a v3 patch.

Fred

-- 
Frederic Danis                            Open Source Technology Centre
frederic.danis@intel.com                              Intel Corporation


      reply	other threads:[~2011-10-17 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 10:56 [PATCH] fix build Frédéric Danis
2011-10-17 11:10 ` Johan Hedberg
2011-10-17 11:16   ` Johan Hedberg
2011-10-17 13:03   ` Frederic Danis
2011-10-17 15:59     ` Frederic Danis [this message]

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=4E9C50DF.5020703@linux.intel.com \
    --to=frederic.danis@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.