From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Constantin Musca <constantinx.musca@intel.com>
Subject: Re: [PATCH 0/3] Package upgrades
Date: Fri, 17 Aug 2012 14:09:03 -0700 [thread overview]
Message-ID: <502EB2EF.8040007@linux.intel.com> (raw)
In-Reply-To: <1344948628-15705-1-git-send-email-constantinx.musca@intel.com>
On 08/14/2012 05:50 AM, Constantin Musca wrote:
> This is another set of package upgrades compiled on all architectures
> and tested using core-image-sato-sdk. Beware that the libxrandr package upgrade
> must be applied after applying the randrproto package upgrade.
>
> Constantin Musca (3):
> pciutils: upgrade to 3.1.10
Merged into OE-Core
> randrproto: upgrade to 1.4.0
> libxrandr: upgrade to 1.4.0
>
These 2 need commit message updates explaining what changed in their
license files. It could be as simple as saying the Year changed, but we
need to know.
Thanks
Sau!
> .../configure.patch | 0
> .../guess-fix.patch | 0
> .../lib-build-fix.patch | 0
> .../makefile.patch | 0
> .../pcimodules-pciutils.diff | 0
> .../{pciutils_3.1.9.bb => pciutils_3.1.10.bb} | 4 ++--
> .../{libxrandr_1.3.2.bb => libxrandr_1.4.0.bb} | 6 +++---
> .../{randrproto_1.3.2.bb => randrproto_1.4.0.bb} | 8 ++++----
> 8 files changed, 9 insertions(+), 9 deletions(-)
> rename meta/recipes-bsp/pciutils/{pciutils-3.1.9 => pciutils-3.1.10}/configure.patch (100%)
> rename meta/recipes-bsp/pciutils/{pciutils-3.1.9 => pciutils-3.1.10}/guess-fix.patch (100%)
> rename meta/recipes-bsp/pciutils/{pciutils-3.1.9 => pciutils-3.1.10}/lib-build-fix.patch (100%)
> rename meta/recipes-bsp/pciutils/{pciutils-3.1.9 => pciutils-3.1.10}/makefile.patch (100%)
> rename meta/recipes-bsp/pciutils/{pciutils-3.1.9 => pciutils-3.1.10}/pcimodules-pciutils.diff (100%)
> rename meta/recipes-bsp/pciutils/{pciutils_3.1.9.bb => pciutils_3.1.10.bb} (92%)
> rename meta/recipes-graphics/xorg-lib/{libxrandr_1.3.2.bb => libxrandr_1.4.0.bb} (72%)
> rename meta/recipes-graphics/xorg-proto/{randrproto_1.3.2.bb => randrproto_1.4.0.bb} (68%)
>
next prev parent reply other threads:[~2012-08-17 21:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 12:50 [PATCH 0/3] Package upgrades Constantin Musca
2012-08-14 12:50 ` [PATCH 1/3] pciutils: upgrade to 3.1.10 Constantin Musca
2012-08-14 12:50 ` [PATCH 2/3] randrproto: upgrade to 1.4.0 Constantin Musca
2012-08-14 12:50 ` [PATCH 3/3] libxrandr: " Constantin Musca
2012-08-17 16:20 ` Saul Wold
2012-08-17 21:09 ` 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-23 11:44 Constantin Musca
2012-08-24 18:36 ` 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=502EB2EF.8040007@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