From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] util-linux-ng: provide libblkid/libuuid/fsck
Date: Fri, 12 Feb 2010 16:18:43 +0100 [thread overview]
Message-ID: <201002121618.44935.marcin@juszkiewicz.com.pl> (raw)
In-Reply-To: <hl3qnh$blr$2@ger.gmane.org>
Dnia piątek, 12 lutego 2010 o 16:05:23 Koen Kooi napisał(a):
> I'm not really fond of the PACKAGES_DYNAMIC bit, but:
It was already present in recipe ;D
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next prev parent reply other threads:[~2010-02-12 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 14:51 Patches to solve libblkid/libuuid version problems Marcin Juszkiewicz
2010-02-12 14:51 ` [PATCH 1/2] e2fsprogs: stop providing libblkid/libuuid/fsck - they are in util-linux-ng Marcin Juszkiewicz
2010-02-12 15:04 ` Koen Kooi
2010-02-12 14:51 ` [PATCH 2/2] util-linux-ng: provide libblkid/libuuid/fsck Marcin Juszkiewicz
2010-02-12 15:05 ` Koen Kooi
2010-02-12 15:18 ` Marcin Juszkiewicz [this message]
2010-02-12 20:12 ` Khem Raj
2010-02-13 5:29 ` Marcin Juszkiewicz
2010-02-12 20:15 ` Patches to solve libblkid/libuuid version problems Khem Raj
2010-02-13 5:26 ` Marcin Juszkiewicz
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=201002121618.44935.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--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