From: Saul Wold <sgw@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Minor fixes
Date: Fri, 05 Oct 2012 09:08:43 -0700 [thread overview]
Message-ID: <506F060B.9050809@linux.intel.com> (raw)
In-Reply-To: <cover.1349267792.git.paul.eggleton@linux.intel.com>
On 10/03/2012 05:37 AM, Paul Eggleton wrote:
> The following changes since commit eb96be4db46039752c44dc37ef676eaac04e3dba:
>
> xf86-video-intel: drop libxvmc dependency (2012-10-03 12:41:03 +0100)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib paule/fixes2
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/fixes2
>
> Paul Eggleton (2):
> buildhistory_analysis: update to use explode_dep_versions2()
> rpmresolve: fix reporting of multiple matches error
>
> meta/lib/oe/buildhistory_analysis.py | 23 +++++++++++++++++----
> meta/recipes-devtools/rpm/rpmresolve/rpmresolve.c | 6 +++---
> meta/recipes-devtools/rpm/rpmresolve_1.0.bb | 2 +-
> 3 files changed, 23 insertions(+), 8 deletions(-)
>
Merged into OE-Core
Thanks
Sau!
next prev parent reply other threads:[~2012-10-05 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 12:37 [PATCH 0/2] Minor fixes Paul Eggleton
2012-10-03 12:37 ` [PATCH 1/2] buildhistory_analysis: update to use explode_dep_versions2() Paul Eggleton
2012-10-03 12:37 ` [PATCH 2/2] rpmresolve: fix reporting of multiple matches error Paul Eggleton
2012-10-05 16:08 ` Saul Wold [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-04 1:31 [PATCH 0/2] Minor fixes Joshua Lock
2012-01-04 11:25 ` Richard Purdie
2011-05-16 20:18 Tom Rini
2011-05-17 18:23 ` 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=506F060B.9050809@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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