From: "Maxin B. John" <maxin.john@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 7/7] libsoup-2.4: upgrade to 2.60.2
Date: Fri, 10 Nov 2017 15:06:48 +0200 [thread overview]
Message-ID: <20171110130648.GA34973@mbabyjoh-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CAJTo0LYrkDO0d8udyN3t_YN-rLFJe34m4tv6q=YCZao_ms2fVA@mail.gmail.com>
Hi Ross,
>Alex's 2.60.1 upgrade was just merged, so can you rebase please.
Sure, will do that.
>Ross
On 10 November 2017 at 12:00, Maxin B. John <maxin.john@intel.com> wrote:
2.58.2 -> 2.60.2
>>Signed-off-by: Maxin B. John <maxin.john@intel.com>
>>---
>>.../libsoup/{libsoup-2.4_2.58.2.bb => libsoup-2.4_2.60.2.bb} | 4 ++--
>>1 file changed, 2 insertions(+), 2 deletions(-)
>>rename meta/recipes-support/libsoup/{libsoup-2.4_2.58.2.bb => libsoup-2.4_2.60.2.bb} (89%)
>>
>>diff --git a/meta/recipes-support/libsoup/libsoup-2.4_2.58.2.bb b/meta/recipes-support/libsoup/libsoup-2.4_2.60.2.bb
Best Regards,
Maxin
next prev parent reply other threads:[~2017-11-10 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 12:00 [PATCH 0/7] package upgrades Maxin B. John
2017-11-10 12:00 ` [PATCH 1/7] ofono: upgrade to 1.21 Maxin B. John
2017-11-10 12:00 ` [PATCH 2/7] harfbuzz: upgrade to 1.6.3 Maxin B. John
2017-11-10 12:00 ` [PATCH 3/7] quota: upgrade to 4.04 Maxin B. John
2017-11-10 12:00 ` [PATCH 4/7] screen: upgrade to 4.6.2 Maxin B. John
2017-11-16 16:09 ` Burton, Ross
2017-11-17 11:20 ` Maxin B. John
2017-11-10 12:00 ` [PATCH 5/7] libproxy: upgrade to 0.4.15 Maxin B. John
2017-11-10 12:00 ` [PATCH 6/7] sqlite3: upgrade to 3.21.0 Maxin B. John
2017-11-10 12:00 ` [PATCH 7/7] libsoup-2.4: upgrade to 2.60.2 Maxin B. John
2017-11-10 12:26 ` Burton, Ross
2017-11-10 13:06 ` Maxin B. John [this message]
2017-11-10 12:35 ` ✗ patchtest: failure for package upgrades (rev2) Patchwork
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=20171110130648.GA34973@mbabyjoh-desk.ger.corp.intel.com \
--to=maxin.john@intel.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