From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] avahi: move systemd support where it belongs
Date: Wed, 13 Mar 2013 17:45:46 +0100 [thread overview]
Message-ID: <20130313164546.GA3260@jama> (raw)
In-Reply-To: <1362503769.11727.24.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On Tue, Mar 05, 2013 at 05:16:09PM +0000, Richard Purdie wrote:
> On Tue, 2013-03-05 at 15:20 +0100, Martin Jansa wrote:
> > On Tue, Mar 05, 2013 at 02:10:25PM +0000, Richard Purdie wrote:
> > > On Mon, 2013-03-04 at 14:25 +0100, Martin Jansa wrote:
> > > > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> > > > ---
> > > > meta/recipes-connectivity/avahi/avahi.inc | 6 +-----
> > > > meta/recipes-connectivity/avahi/avahi_0.6.31.bb | 6 ++++++
> > > > 2 files changed, 7 insertions(+), 5 deletions(-)
> > >
> > > "where it belongs"? Is this due to the avahi-ui recipe?
> >
> > Yes, avahi-ui is overwriting PACKAGES and systemd.bbclass was showing
> > warnings since this systemd was added to avahi.inc
>
> In future please put that in the commit message. I added it this time...
Thanks for adding it, I've reported this issue with longer description
on 27 Feb 2013, then I forgot about it and because I got no reply from
developer who introduced it I've fixed later in hurry to get
meta-systemd parsing again.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-03-13 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 13:25 [PATCH] avahi: move systemd support where it belongs Martin Jansa
2013-03-05 14:10 ` Richard Purdie
2013-03-05 14:20 ` Martin Jansa
2013-03-05 17:16 ` Richard Purdie
2013-03-13 16:45 ` Martin Jansa [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=20130313164546.GA3260@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.