From: Martin Jansa <martin.jansa@gmail.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] oestats-client: add metadata_scm inherit after base.bbclass split in 89b7e433719f43f1c36c76cb8856d559014e99bc
Date: Thu, 25 Mar 2010 15:52:05 +0100 [thread overview]
Message-ID: <20100325145204.GD3458@jama> (raw)
In-Reply-To: <20100325154613.d1dfe88a.ospite@studenti.unina.it>
On Thu, Mar 25, 2010 at 03:46:13PM +0100, Antonio Ospite wrote:
> On Thu, 25 Mar 2010 15:24:23 +0100
> Martin Jansa <martin.jansa@gmail.com> wrote:
>
> [...]
> > --- a/classes/oestats-client.bbclass
> > +++ b/classes/oestats-client.bbclass
> > @@ -9,6 +9,8 @@
> > # OESTATS_BUILDER = "some_nickname"
> > #
> >
> > +inherit metadata_scm
> > +
>
> Hi Martin, this makes sense indeed, but can you please explain if/why my
> previous patch[1] is not complete? In other words can oestats-client
> be used without base.bbclass? Or is that "just" to make the inheritance
> explicit?
>
> Thanks,
> Antonio
>
> [1]
> http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-March/018675.html
Hi Antonio,
ah, sorry I overlooked your patch in ML, for me your patch is as good
as mine and maybe better.
I just walk into the same issue today when RP sent me patch fixing event.data
availability for oestats-client with bitbake master (before I had 2
constants there to work-arround this issue).
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
prev parent reply other threads:[~2010-03-25 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 14:24 [PATCH] oestats-client: add metadata_scm inherit after base.bbclass split in 89b7e433719f43f1c36c76cb8856d559014e99bc Martin Jansa
2010-03-25 14:46 ` Antonio Ospite
2010-03-25 14:52 ` 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=20100325145204.GD3458@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ospite@studenti.unina.it \
/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.