From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Fix udev pulling in libvolume-id-dev
Date: Sun, 18 Jan 2009 22:56:47 -0200 [thread overview]
Message-ID: <87zlhoglkg.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <20090118041800.GA852@denix.org> (Denys Dmytriyenko's message of "Sat\, 17 Jan 2009 23\:18\:00 -0500")
Denys Dmytriyenko <denis@denix.org> writes:
>> I guess we need more Core devs to look into this issue to verify the safety of
>> this patch.
>
> Otavio was using patched package.bbclass (as mentioned above) for a few days
> and found it working fine and fixing udev issue for him.
>
> Khem, please let me know if you still disagree with the proposed fix. Or if
> anybody else has any objections, please speak up. Otherwise I'd like to check
> in the fix for the package.bbclass in a day or two. Thanks.
Yes, I support this patch since it does solve the issue for me.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
prev parent reply other threads:[~2009-01-19 1:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 6:14 [RFC] Fix udev pulling in libvolume-id-dev Denys Dmytriyenko
2009-01-15 6:56 ` Koen Kooi
2009-01-15 7:41 ` Khem Raj
2009-01-15 11:10 ` Koen Kooi
2009-01-15 18:53 ` Khem Raj
2009-01-15 18:57 ` Koen Kooi
2009-03-14 1:08 ` Denys Dmytriyenko
2009-01-15 19:20 ` Tom Rini
2009-01-15 19:41 ` Koen Kooi
2009-01-15 15:58 ` Denys Dmytriyenko
2009-01-15 7:37 ` Khem Raj
2009-01-15 15:51 ` Denys Dmytriyenko
2009-01-18 4:18 ` Denys Dmytriyenko
2009-01-19 0:56 ` Otavio Salvador [this message]
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=87zlhoglkg.fsf@neumann.lab.ossystems.com.br \
--to=otavio@debian.org \
--cc=openembedded-devel@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