From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Subject: Re: [PATCH 1/2] devtool: finish: Keep patches ordered when updating bbappend
Date: Tue, 24 Sep 2019 09:08:02 +1200 [thread overview]
Message-ID: <4862090.aWbVv4fHtx@linux.fritz.box> (raw)
In-Reply-To: <20190920203043.1449-1-pkj@axis.com>
On Saturday, 21 September 2019 8:30:42 AM NZST Peter Kjellerstedt wrote:
> From: Niclas Svensson <niclass@axis.com>
>
> The _get_patchset_revs() function returns the patches in an
> OrderedDict to keep them ordered. However, this information was lost
> when the patches were added to the bbappend file.
Both this and 2/2 look good to me.
Acked-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Thanks
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2019-09-23 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 20:30 [PATCH 1/2] devtool: finish: Keep patches ordered when updating bbappend Peter Kjellerstedt
2019-09-20 20:30 ` [PATCH 2/2] devtool: finish: Add suppport for the --no-clean option Peter Kjellerstedt
2019-09-23 21:08 ` Paul Eggleton [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=4862090.aWbVv4fHtx@linux.fritz.box \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.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