All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH 1/2] chromium: Add PACKAGECONFIG for disabling API keys info bar
Date: Wed, 30 Jul 2014 19:23:23 +0200	[thread overview]
Message-ID: <20140730172323.GS16445@jama> (raw)
In-Reply-To: <CAMKF1soqe5woG5DcO9FP0tPVpprtgnHKMY4W8HcThZWTdncioA@mail.gmail.com>

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

On Wed, Jul 30, 2014 at 10:01:42AM -0700, Khem Raj wrote:
> On Wed, Jul 30, 2014 at 6:02 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
> > As I explained, this is the requirement for some projects we've been
> > involved with. The idea here is to share it in a 'reusable' way and
> > avoid this patch to be kept private for no good reason.
> >
> 
> than have it in bbappends would solve it.

I agree with Otavio, that having just PACKAGECONFIG switch in .bbappend
or distro config is simpler than reinventing this .patch in each layer
which needs that.

> 
> > I think it is fine as is.
> 
> For you yes I understand, do you have say of other folks who use this layer ?

He only adds the option, it even isn't enabled by default, so FWIW I'm
fine with this.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

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

  parent reply	other threads:[~2014-07-30 17:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 10:22 [meta-browser][PATCH 1/2] chromium: Add PACKAGECONFIG for disabling API keys info bar Carlos Rafael Giani
2014-07-29 10:22 ` [meta-browser][PATCH 2/2] chromium: Add recipe for version 37.0.2062.0 Carlos Rafael Giani
2014-08-01 12:57   ` Otavio Salvador
2014-07-29 20:35 ` [meta-browser][PATCH 1/2] chromium: Add PACKAGECONFIG for disabling API keys info bar Khem Raj
2014-07-29 21:51   ` Otavio Salvador
2014-07-30  2:28     ` Khem Raj
2014-07-30 13:02       ` Otavio Salvador
2014-07-30 17:01         ` Khem Raj
2014-07-30 17:20           ` Otavio Salvador
2014-07-30 17:23           ` Martin Jansa [this message]
2014-07-30 17:29             ` Khem Raj
2014-08-01 12:56 ` Otavio Salvador

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=20140730172323.GS16445@jama \
    --to=martin.jansa@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.