All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH] autofs: Remove systemd related things.
Date: Thu, 10 Jan 2013 07:33:09 -0500	[thread overview]
Message-ID: <20130110123309.GD3594@windriver.com> (raw)
In-Reply-To: <20130110123006.GC3594@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

[Re: [oe] [meta-networking][PATCH] autofs: Remove systemd related things.] On 13.01.10 (Thu 07:30) Joe MacDonald wrote:

> [Re: [oe] [meta-networking][PATCH] autofs: Remove systemd related things.] On 13.01.10 (Thu 12:58) Andreas Müller wrote:
> 
> > On Thu, Jan 10, 2013 at 12:53 PM, Andreas Müller
> > <schnitzeltony@googlemail.com> wrote:
> > > On Thu, Jan 10, 2013 at 11:44 AM, Noor, Ahsan <noor_ahsan@mentor.com> wrote:
> > >> From: Noor Ahsan <noor_ahsan@mentor.com>
> > >>
> > >> * Autofs was being inherited from systemd. This class is only
> > >> present in meta-systemd. So bitbake was giving parse error
> > >> about systemd class. So removed systemd from inherit and
> > >> removed SYSTEMD_PACKAGES and SYSTEMD_SERVICE.
> > > Is this still true after auto BBMASKing?
> > I misread the patch so please forget previous mail. But it would be
> > nice to have an systemd append.
> 
> Yeah, I agree.  I'll merge this patch,

Unless it's already been merged.  :-)

> but please also consider sending a patch for meta-systemd that has the
> appropriate bbappends.

-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-01-10 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 10:44 [meta-networking][PATCH] autofs: Remove systemd related things Noor, Ahsan
2013-01-10 11:53 ` Andreas Müller
2013-01-10 11:58   ` Andreas Müller
2013-01-10 12:30     ` Joe MacDonald
2013-01-10 12:33       ` Joe MacDonald [this message]
2013-01-10 12:31     ` Martin Jansa

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=20130110123309.GD3594@windriver.com \
    --to=joe.macdonald@windriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.