From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Saul Wold <saul.wold@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libsoup-2.4: upgrade to 2.45.92
Date: Mon, 24 Mar 2014 16:15:22 +0800 [thread overview]
Message-ID: <532FE99A.7070200@windriver.com> (raw)
In-Reply-To: <CAJTo0LZEQzZYt+G=3OyzKLdceXeKZ2dHD2gDOVEJBD+yhiAc6g@mail.gmail.com>
On 03/24/2014 04:09 PM, Burton, Ross wrote:
> On 24 March 2014 07:40, Hongxu Jia <hongxu.jia@windriver.com> wrote:
>> There was a error about mips-gcc optimization while building
>> libsoup-2.4 2.45.3 with DEBUG_OPTIMIZATION enabled, the 2.45.92
>> have fixed this issue.
> .92 means "beta release" in GNOME versioning, so not only is this a
> new upstream release (when we've frozen) but it's also not a stable
> release. Please backport the patch instead of upgrading.
OK, I will backport to 2.45.3
//Hongxu
>
> Ross
prev parent reply other threads:[~2014-03-24 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 7:40 [PATCH 0/1] libsoup-2.4: upgrade to 2.45.92 Hongxu Jia
2014-03-24 7:40 ` [PATCH 1/1] " Hongxu Jia
2014-03-24 7:57 ` Hongxu Jia
2014-03-24 9:06 ` Burton, Ross
2014-03-25 4:12 ` Hongxu Jia
2014-03-24 8:09 ` Burton, Ross
2014-03-24 8:15 ` Hongxu Jia [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=532FE99A.7070200@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=saul.wold@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 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.