From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] udev fixes
Date: Tue, 1 Nov 2011 16:14:27 +0000 [thread overview]
Message-ID: <cover.1320163967.git.paul.eggleton@linux.intel.com> (raw)
Some rebased OE-core patches from Holger that got lost on the
openembedded-devel list.
The following changes since commit eff22e23b4c7d88254a6ac420bf0860f1fe2cd3e:
coreutils: Add missing PR bump (2011-11-01 15:45:42 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/udev-glib
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/udev-glib
Holger Hans Peter Freyther (2):
udev: Fix the packaging of libgudev
udev: Split out consolekit and udev-acl
meta/recipes-core/udev/udev-new.inc | 10 ++++++++--
meta/recipes-core/udev/udev_164.bb | 2 +-
2 files changed, 9 insertions(+), 3 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-11-01 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 16:14 Paul Eggleton [this message]
2011-11-01 16:14 ` [PATCH 1/2] udev: Fix the packaging of libgudev Paul Eggleton
2011-11-01 16:14 ` [PATCH 2/2] udev: Split out consolekit and udev-acl Paul Eggleton
2011-11-01 16:31 ` Koen Kooi
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=cover.1320163967.git.paul.eggleton@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox