Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: UDEV-145??
Date: Mon, 19 Dec 2011 10:20:35 -0800	[thread overview]
Message-ID: <4EEF8073.2040205@linux.intel.com> (raw)
In-Reply-To: <4EEBC476.20108@linux.intel.com>

On 16/12/11 14:21, Saul Wold wrote:
> 
> Does anyone know why we might be keeping this older version around?  I
> know that in the past there were kernel <-> udev issues. Are most usages
> now using current kernels and udev?

I was wondering the same thing. I have a WIP patch series to drop the
old version and the old inc file.

Further I'd like to try and get meta-oe using at least most of the
oe-core udev, I've not looked at the differences there yet.

Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre



  reply	other threads:[~2011-12-19 18:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 22:21 UDEV-145?? Saul Wold
2011-12-19 18:20 ` Joshua Lock [this message]
2011-12-20 13:35   ` UDEV-145?? Otavio Salvador
2011-12-20 13:48     ` UDEV-145?? Koen Kooi
2011-12-20 14:26       ` UDEV-145?? Otavio Salvador

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=4EEF8073.2040205@linux.intel.com \
    --to=josh@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