All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH V2 6/7] blacklist.bbclass: Move to meta-angstrom
Date: Sun, 5 Aug 2012 15:06:15 -0700	[thread overview]
Message-ID: <CAMKF1sr8cKuU79Fc9=uXUo0-u8V0vhOg9PGOqb7m8jeBDR4bNw@mail.gmail.com> (raw)
In-Reply-To: <CABcZANnEmASgH3wrk7TZOpe3BaK+o6oRPyvAo6SadtybgqDWJg@mail.gmail.com>

On Sun, Aug 5, 2012 at 2:37 PM, Chris Larson <clarson@kergoth.com> wrote:
>
> This doesn't make much sense to me. It's impossible to know what all
> layers use a given piece of functionality, particularly ones that
> aren't published in public places, so expecting every person changing
> something in oe-core will go and submit changes to every layer that
> exists is entirely unreasonable. If you maintain a layer, it's your
> responsibility to make sure your layer retains compatibility with
> upstream. It's not upstream's responsibility to make sure everyone
> using their functionality stays compatible.

I would agree in general. In this given case this feature was taken
from meta-oe to begin with
so my point is if you moved it from meta-oe then make sure that its
removed from meta-oe



  reply	other threads:[~2012-08-05 22:18 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
2012-08-05 19:44         ` Khem Raj
2012-08-05 21:37         ` Chris Larson
2012-08-05 22:06           ` Khem Raj [this message]
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='CAMKF1sr8cKuU79Fc9=uXUo0-u8V0vhOg9PGOqb7m8jeBDR4bNw@mail.gmail.com' \
    --to=raj.khem@gmail.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.