From: Apelete Seketeli <apelete@seketeli.net>
To: openembedded-devel@openembedded.org
Cc: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Subject: [oe-classic][udev][PATCH 0/5] update recipe SRC_URI
Date: Sat, 23 Jun 2012 21:16:36 +0200 [thread overview]
Message-ID: <20120623191635.GN4845@hermes> (raw)
Hello,
Some of the udev source tarballs are no longer available on the
kernel.org repository. As a consequence, the corresponding recipes in
oe classic fail to build. I found a mirror where these source tarballs
are still available, and updated the recipes in oe classic
accordingly.
The five patches that come as a follow-up of this message are what
it's all about.
Apelete Seketeli (5):
udev: update SRC_URI of udev-151 recipe
udev: update SRC_URI of udev-154 recipe
udev: update SRC_URI of udev-162 recipe
udev: update SRC_URI of udev-165 recipe
udev: update SRC_URI of udev-168 recipe
recipes/udev/udev_151.bb | 2 +-
recipes/udev/udev_154.bb | 2 +-
recipes/udev/udev_162.bb | 2 +-
recipes/udev/udev_165.bb | 2 +-
recipes/udev/udev_168.bb | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
--
1.7.10
--
Apelete
next reply other threads:[~2012-06-23 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 19:16 Apelete Seketeli [this message]
2012-06-23 19:19 ` [oe-classic][udev][PATCH 1/5] udev: update SRC_URI of udev-151 recipe Apelete Seketeli
2012-06-23 19:20 ` [oe-classic][udev][PATCH 2/5] udev: update SRC_URI of udev-154 recipe Apelete Seketeli
2012-06-23 19:21 ` [oe-classic][udev][PATCH 3/5] udev: update SRC_URI of udev-162 recipe Apelete Seketeli
2012-06-23 19:22 ` [oe-classic][udev][PATCH 4/5] udev: update SRC_URI of udev-165 recipe Apelete Seketeli
2012-06-23 19:23 ` [oe-classic][udev][PATCH 5/5] udev: update SRC_URI of udev-168 recipe Apelete Seketeli
2012-06-27 16:36 ` [oe-classic][udev][PATCH 0/5] update recipe SRC_URI Apelete Seketeli
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=20120623191635.GN4845@hermes \
--to=apelete@seketeli.net \
--cc=kristoffer.ericson@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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