Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH V2 6/7] blacklist.bbclass: Move to meta-angstrom
Date: Sun, 05 Aug 2012 13:41:33 +0200	[thread overview]
Message-ID: <jvlm56$r75$1@dough.gmane.org> (raw)
In-Reply-To: <CAMKF1sqBGOR=f-e+D8zrguifFbsRzkVLtLsOCf4rxaGKiwPK2Q@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 04-08-12 22:47, Khem Raj schreef:
> On Sat, Aug 4, 2012 at 1:36 PM, Koen Kooi <koen@dominion.thruhere.net>
> wrote:
>> 
>> As said before, this class isn't angstrom specific and it won't move
>> back to angstrom.
> 
> koen no one else is using it other than angstrom. but it interferes with
> similar class from OE-Core

I guess oe-core people need to be less anti-social with other layers then
and provide migration patches.

> so essentially you want to keep a feature thats just used by angstrom in
> a non angstrom layer?

No, I want the class deleted. But as I keep saying, the class was moved to
meta-oe on request because is was most certainly not angstrom specific. And
as angstrom maintainer I have no intent to add it back to the angstrom
layer. So your commit message is entirely wrong.

> doent sound logical to me. Would it be acceptable if angstrom used this
> feature from OE-Core as well ? then it will remove the usecase
> completely.

I keep waiting on the person that pushed it to oe-core to provide patches
for distro layers using the old functionality, see above.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQHlvtMkyGM64RGpERAlM+AJ0QIjUUJazAAA39xptb5OTVbU7GkQCgumJT
FFtbzZWd8sI4w3gPZJTLeho=
=mlaZ
-----END PGP SIGNATURE-----




  parent reply	other threads:[~2012-08-05 11:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 18:56 [meta-systemd][PATCH V2 1/7] systemd: Upgrade to 187 Khem Raj
2012-07-31 18:56 ` [meta-systemd][PATCH V2 2/7] busybox: stopping systemd-kmsg-syslogd is not needed Khem Raj
2012-07-31 18:56 ` [meta-systemd][PATCH V2 3/7] busybox-syslog.service.in: Create alias for syslog.service Khem Raj
2012-07-31 18:56 ` [meta-systemd][PATCH V2 4/7] systemd: Use cross cpp Khem Raj
2012-07-31 18:56 ` [meta-oe][PATCH V2 5/7] testlab.bbclass: Delete Khem Raj
2012-07-31 18:56 ` [meta-oe][PATCH V2 6/7] blacklist.bbclass: Move to meta-angstrom Khem Raj
2012-07-31 19:07   ` Koen Kooi
2012-07-31 19:24     ` Chris Larson
2012-07-31 19:43     ` Martin Jansa
2012-07-31 20:46       ` Khem Raj
2012-08-04 20:36   ` Koen Kooi
2012-08-04 20:47     ` Khem Raj
2012-08-04 21:56       ` Philip Balister
2012-08-05 11:41       ` Koen Kooi [this message]
2012-08-05 19:44         ` Khem Raj
2012-08-05 21:37         ` Chris Larson
2012-08-05 22:06           ` Khem Raj
2012-08-06  7:43           ` Koen Kooi
2012-08-07  2:38             ` Khem Raj
2012-07-31 18:56 ` [meta-oe][PATCH V2 7/7] kernel.bbclass: Rename to machine_kernel_pr.bbclass which provides added functionality Khem Raj
2012-08-01 17:38   ` Otavio Salvador
2012-08-01 22:31     ` Khem Raj
2012-08-01 15:11 ` [meta-systemd][PATCH V2 1/7] systemd: Upgrade to 187 Koen Kooi
2012-08-01 22:56   ` Khem Raj
2012-08-02  8:11     ` Paul Eggleton
2012-08-03 10:32       ` Khem Raj
2012-08-03 12:38         ` Koen Kooi
2012-08-03 14:41           ` Khem Raj
2012-08-03 15:36             ` Koen Kooi
2012-08-03 18:39               ` Khem Raj
2012-08-03 18:42                 ` Martin Jansa
2012-08-03 19:08                 ` Koen Kooi
2012-08-04 20:10               ` Khem Raj
2012-08-04 20:35                 ` Koen Kooi
2012-08-04 20:50                   ` Khem Raj
2012-08-05 11:42                     ` Koen Kooi
2012-08-05 11:53                       ` Philip Balister
2012-08-05 19:40                         ` Khem Raj

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='jvlm56$r75$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox