From: Fan Xin <fan.xin@jp.fujitsu.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] wpa-supplicant: upgrade to 2.5
Date: Thu, 19 Nov 2015 18:25:13 +0900 [thread overview]
Message-ID: <564D9579.60602@jp.fujitsu.com> (raw)
In-Reply-To: <CAJTo0Laiibw3uxt1OHQK0MfTGcWrJsQYduPunx8sYJc0iq3+Gw@mail.gmail.com>
Hi
> It looks like you generated a patch and then pasted it into the
> Thunderbird composer, which means long lines wrap and the patch
> corrupts. Can you either send the patch without line wrapping or
> ideally using git-send-email directly?
Sorry for the wrong way to send patch.
I will re-send the patch using git-send-email.
Best Regards,
Fan
On 2015年11月17日 00:03, Burton, Ross wrote:
>
> On 16 November 2015 at 10:37, Fan Xin <fan.xin@jp.fujitsu.com
> <mailto:fan.xin@jp.fujitsu.com>> wrote:
>
> wpa-supplicant: upgrade to 2.5
>
> 1. upgrade to 2.5
> 2. remove eight patches since they have been applied in 2.5
> 3. update SRC_URI, HOMEPAGE and BUGTRACKER to use w1.fi
> <http://w1.fi> instead
>
> Signed-off-by: Fan Xin <fan.xin at jp.fujitsu.com
> <http://jp.fujitsu.com>>
>
>
> It looks like you generated a patch and then pasted it into the
> Thunderbird composer, which means long lines wrap and the patch
> corrupts. Can you either send the patch without line wrapping or
> ideally using git-send-email directly?
>
> Thanks,
> Ross
next prev parent reply other threads:[~2015-11-19 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 7:27 [PATCH] wpa-supplicant: upgrade to 2.5 Fan Xin
2015-11-11 18:44 ` Burton, Ross
2015-11-13 0:50 ` Fan Xin
2015-11-16 10:37 ` [PATCH v2] " Fan Xin
2015-11-16 15:03 ` Burton, Ross
2015-11-19 9:25 ` Fan Xin [this message]
2015-11-12 8:43 ` [PATCH] " Maxin B. John
2015-11-13 0:56 ` Fan Xin
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=564D9579.60602@jp.fujitsu.com \
--to=fan.xin@jp.fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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