Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Constantin Musca <constantinx.musca@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Package upgrades
Date: Fri, 24 Aug 2012 11:36:47 -0700	[thread overview]
Message-ID: <5037C9BF.8020003@linux.intel.com> (raw)
In-Reply-To: <1345722302-25467-1-git-send-email-constantinx.musca@intel.com>

On 08/23/2012 04:44 AM, Constantin Musca wrote:
> This is another set of package upgrades compiled on all architectures
> and tested using core-image-sato.
>
> Constantin Musca (3):
>    foomatic-filters: upgrade to 4.0.17
>    libnfsidmap: upgrade to 0.25
>    dbus-glib: upgrade to 0.100
>
>   .../nfs-utils/files/fix-ac-prereq.patch            |    6 ++----
>   .../{libnfsidmap_0.24.bb => libnfsidmap_0.25.bb}   |    6 +++---
>   .../no-examples.patch                              |    0
>   .../test-install-makefile.patch                    |    0
>   .../test-service-glib-include-glib-only.patch      |   20 --------------------
>   meta/recipes-core/dbus/dbus-glib.inc               |    1 -
>   .../dbus/{dbus-glib_0.98.bb => dbus-glib_0.100.bb} |    6 +++---
>   ...ilters_4.0.16.bb => foomatic-filters_4.0.17.bb} |    6 +++---
>   8 files changed, 11 insertions(+), 34 deletions(-)
>   rename meta/recipes-connectivity/nfs-utils/{libnfsidmap_0.24.bb => libnfsidmap_0.25.bb} (74%)
>   rename meta/recipes-core/dbus/{dbus-glib-0.98 => dbus-glib-0.100}/no-examples.patch (100%)
>   rename meta/recipes-core/dbus/{dbus-glib-0.98 => dbus-glib-0.100}/test-install-makefile.patch (100%)
>   delete mode 100644 meta/recipes-core/dbus/dbus-glib-0.98/test-service-glib-include-glib-only.patch
>   rename meta/recipes-core/dbus/{dbus-glib_0.98.bb => dbus-glib_0.100.bb} (13%)
>   rename meta/recipes-extended/foomatic/{foomatic-filters_4.0.16.bb => foomatic-filters_4.0.17.bb} (90%)
>
Merged into OE-Core

Thanks
	Sau!




  parent reply	other threads:[~2012-08-24 18:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 11:44 [PATCH 0/3] Package upgrades Constantin Musca
2012-08-23 11:45 ` [PATCH 1/3] foomatic-filters: upgrade to 4.0.17 Constantin Musca
2012-08-23 11:45 ` [PATCH 2/3] libnfsidmap: upgrade to 0.25 Constantin Musca
2012-08-23 11:45 ` [PATCH 3/3] dbus-glib: upgrade to 0.100 Constantin Musca
2012-08-24 18:36 ` Saul Wold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-20  1:11 [PATCH 0/3] Package upgrades Denys Dmytriyenko
2018-03-29 22:41 ` Denys Dmytriyenko
2018-03-29 23:39   ` Andre McCurdy
2018-03-30  0:17     ` Denys Dmytriyenko
2018-03-30  1:38       ` Khem Raj
2018-03-30  2:34         ` Denys Dmytriyenko
2018-03-30  2:41           ` Khem Raj
2018-03-30  3:30             ` Denys Dmytriyenko
2018-03-30  8:36   ` Richard Purdie
2015-05-11  6:48 [PATCH 0/3] Package Upgrades Robert Yang
2015-04-10  8:31 Robert Yang
2014-06-03  1:41 Chen Qi
2014-03-12  1:57 Chen Qi
2013-11-26 12:39 [PATCH 0/3] Package upgrades Cristiana Voicu
2013-10-24 18:29 Marko Lindqvist
2013-08-05  8:28 Cristiana Voicu
2012-12-10  8:08 Constantin Musca
2012-08-14 12:50 Constantin Musca
2012-08-17 21:09 ` Saul Wold
2012-08-13 14:27 Constantin Musca
2012-08-17 20:56 ` 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=5037C9BF.8020003@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=constantinx.musca@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox