From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/7] libsoup-2.4: Update from 2.42.1 to 2.43.1
Date: Fri, 24 May 2013 10:36:22 +0100 [thread overview]
Message-ID: <2891613.OHSbzUYamb@helios> (raw)
In-Reply-To: <CAJTo0La4fnedhZLWVTGruWSbP_MhOLa5WFW1_6-0KJrCMp_4_Q@mail.gmail.com>
On Friday 24 May 2013 10:30:00 Burton, Ross wrote:
> NACK. libsoup is GNOMEy, so odd minor versions indicate development
> releases. Stick with 2.42.x until 2.44.x appears.
Could we just add some logic to distrodata.bbclass so that we don't get
reports of needing to upgrade to these unstable releases?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-24 9:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 9:18 [PATCH 0/7] Package Upgrades Ionut Radu
2013-05-24 9:18 ` [PATCH 1/7] apt: Updated from 0.9.7.8 to 0.9.8.1 Ionut Radu
2013-05-24 9:18 ` [PATCH 2/7] freetype: Updated from 2.4.11 to 2.4.12 Ionut Radu
2013-05-24 9:29 ` Burton, Ross
2013-05-24 9:32 ` Paul Eggleton
2013-05-24 9:18 ` [PATCH 3/7] libtasn1: Updated from 2.14 to 3.3 Ionut Radu
2013-05-24 9:18 ` [PATCH 4/7] libsoup-2.4: Update from 2.42.1 to 2.43.1 Ionut Radu
2013-05-24 9:30 ` Burton, Ross
2013-05-24 9:36 ` Paul Eggleton [this message]
2013-05-24 10:40 ` Ciobanu, Emilia Maria Silvia
2013-05-24 10:49 ` Paul Eggleton
2013-05-24 9:18 ` [PATCH 5/7] matchbox-keyboard: Update to 0.0+gitAUTOINCa+a17b1135daab9eb4cd3647c02e82687f96d93619 Ionut Radu
2013-05-24 9:24 ` Martin Jansa
2013-05-24 9:26 ` Burton, Ross
2013-05-24 9:31 ` Radu, IonutX
2013-05-24 9:18 ` [PATCH 6/7] matchbox-terminal: Updated to 0.0+gitAUTOINC+452bca253492a97a587f440289b9ab27d217353e Ionut Radu
2013-05-24 9:27 ` Martin Jansa
2013-05-24 9:18 ` [PATCH 7/7] settings-daemon: Updated to 0.0+gitAUTOINC+9a99528b02255450db81176abd9bbcc1dab9a4c1 Ionut Radu
2013-05-24 9:31 ` Burton, Ross
2013-05-27 23:14 ` [PATCH 0/7] Package Upgrades Saul Wold
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=2891613.OHSbzUYamb@helios \
--to=paul.eggleton@linux.intel.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 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.