Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH v2] util-linux: split fsck* into its own subpackage
Date: Fri, 07 Oct 2011 15:36:25 +0100	[thread overview]
Message-ID: <1317998193.8533.2.camel@ted> (raw)
In-Reply-To: <1317913185-11345-1-git-send-email-koen@dominion.thruhere.net>

On Thu, 2011-10-06 at 16:59 +0200, Koen Kooi wrote:
> This will allow systemd to run /sbin/fsck without dragging in all of util-linux
> 
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
>  meta/recipes-core/util-linux/util-linux.inc       |   16 +++++++++++++---
>  meta/recipes-core/util-linux/util-linux_2.19.1.bb |    2 +-
>  2 files changed, 14 insertions(+), 4 deletions(-)

Merged to master, thanks.

Richard




      reply	other threads:[~2011-10-07 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 14:59 [PATCH v2] util-linux: split fsck* into its own subpackage Koen Kooi
2011-10-07 14:36 ` Richard Purdie [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=1317998193.8533.2.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=koen@dominion.thruhere.net \
    --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