From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Fan Xin <fan.xin@jp.fujitsu.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sed: Upgrade 4.2.2 -> 4.4
Date: Fri, 02 Jun 2017 09:31:00 +0100 [thread overview]
Message-ID: <1496392260.6630.81.camel@linuxfoundation.org> (raw)
In-Reply-To: <1496391315-26446-1-git-send-email-fan.xin@jp.fujitsu.com>
On Fri, 2017-06-02 at 17:15 +0900, Fan Xin wrote:
> 1. Upgrade sed from 4.2.2 to 4.4
>
> 2. Update the SRC_URI
> The format of archive file is changed from .tar.gz to .tar.xz
>
> 3. Rename the folder from sed-4.2.2 to sed
> No need to update the folder name when version upgrade
>
> 4. Delete unncessary patch file due to the applied file is not exist.
> sed-add-ptest.patch
That patch touches three files. Could you explain more about why this
patch is no longer required as I don't quite understand what you mean
here?
Cheers,
Richard
prev parent reply other threads:[~2017-06-02 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 8:15 [PATCH] sed: Upgrade 4.2.2 -> 4.4 Fan Xin
2017-06-02 8:30 ` Dengke Du
2017-06-02 8:31 ` Richard Purdie [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=1496392260.6630.81.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=fan.xin@jp.fujitsu.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox