Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leandro Dorileo <leandro.maciel.dorileo@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 0/3] systemd and dbus: split modules into packages
Date: Tue, 05 May 2015 14:00:49 -0300	[thread overview]
Message-ID: <5548F741.5050809@intel.com> (raw)
In-Reply-To: <1430775804-30845-1-git-send-email-bruno.bottazzini@intel.com>

Hi Bruno,

Now I think the patchset looks way much better.

Thanks...

--
Dorileo



On 05/04/2015 06:43 PM, Bruno Bottazzini wrote:
> Differences from V1:
> - Making sure that we don't change default configuration as Anders and
>    Otavio suggested.
> - Changing EXTRA_OECONF flags to use it with PAKAGECONFIG as Anders pointed
>    in the review.
> - New patch that verifies if journal-flush.service exists.
>    It may not exists depending on package configuration that the users want to
>    be installed or removed.
>
> Bruno Bottazzini (2):
>    systemd: Verify if journal-flush.service exists.
>    systemd: split modules into packages
>
> Gustavo Sverzut Barbieri (1):
>    dbus: split tools package.
>
>   meta/recipes-core/dbus/dbus.inc          |    9 +-
>   meta/recipes-core/systemd/systemd_219.bb | 1146 ++++++++++++++++++++++++++----
>   2 files changed, 1025 insertions(+), 130 deletions(-)
>
> --
> 2.3.7
>



      parent reply	other threads:[~2015-05-05 17:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 21:43 [PATCH V2 0/3] systemd and dbus: split modules into packages Bruno Bottazzini
2015-05-04 21:43 ` [PATCH V2 1/3] dbus: split tools package Bruno Bottazzini
2015-05-04 21:43 ` [PATCH V2 2/3] systemd: Verify if journal-flush.service exists Bruno Bottazzini
2015-05-04 21:43 ` [PATCH V2 3/3] systemd: split modules into packages Bruno Bottazzini
2015-05-05 20:01   ` Anders Darander
2015-05-05 20:38     ` Leandro Dorileo
2015-05-05 21:57       ` Bottazzini, Bruno
2015-05-05 22:04   ` Otavio Salvador
2015-05-05 17:00 ` Leandro Dorileo [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=5548F741.5050809@intel.com \
    --to=leandro.maciel.dorileo@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