All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Franco <alejandro.franco@linux.intel.com>
To: Paul Eggleton <paul.eggleton@intel.com>, yocto@yoctoproject.org
Subject: Re: [PATCHv2] [layerindex-web] recipe blacklisted information
Date: Tue, 1 Dec 2015 18:47:27 -0600	[thread overview]
Message-ID: <565E3F9F.7070609@linux.intel.com> (raw)
In-Reply-To: <2124896.i64Oee0N8V@peggleto-mobl.ger.corp.intel.com>


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

Hmm I swear reading that, the message I get is that one should inherit
the blacklist class in local.conf (if not on there already) and also set
the (varflag) value of that variable for your recipe there.

Perhaps the part that reads "the blacklist class, which the recipe must
inherit globally" suffers from a wording issue, saying "must inherit"
rather than "by default inherits".

I guess next step here's creating a documentation bug report/ticket.

Meanwhile, the changes are ready and showcased here [1]

I'll let you review this before I sent v3 of the patch ;)

@Belen, I did something possibly hacky with the css in order to
accomplish this, the warn blockquote is set to take 100% of the
horizontal space available within the alert div. If that runs counter to
some design philosophy (perhaps specifically since we're using
bootstrap) let me know please :b

The hovering now only works within a TD...

Alex Franco

[1] http://yctb03.ostc.intel.com:9999/

On 12/01/2015 01:11 PM, Paul Eggleton wrote:
> On Tue, 01 Dec 2015 12:26:18 Alex Franco wrote:
>> @Martin, I think this information about blacklisting would indeed be
>> very useful, thanks for your input as always.
>>
>> @Belen, yes indeed I noticed the label also hovers even when no tooltip
>> is present, this bugged me a little too to be honest! No worries though,
>> I can fix the hover situation and also add in the link to the
>> documentation.
>> @All: I suppose the link should go to:
>>
>>
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-> PNBLACKLIST
>
> Yes, that's really the only place we could link to; unfortunately
though I
> just noticed there is an obvious mistake in there about inheriting the
class
> globally within the recipe (a contradiction); it also doesn't mention the
> class is inherited globally by default.
>
> Cheers,
> Paul
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJWXj+bAAoJEPR9uwMY2lTLYT4H/1CUZHoE9nSCRhB9zRmbe/gq
fYxLRCHt34DZvTjA5N+KNJd80z9NOo1q6jWKu0Rh6XHQgExTuruzi1nkyJ4BIoRD
ziexugIXyYFJIymT6m38sZfwBV+KA+FSoTKplj+ZjLdC3HzSpKoVmFHO/wx/coC+
s90uyagoFYtAb/cmaLJmZW+q9J9v/UtAop4CD7nuLVhJvVxYIe2/Cub2MGrZy5P/
EcciqfI8Cn/cWoGfptoRmBOA2yjAR1SqZtwWCOLze68eiRkV/P/3uMgMOy9i2feM
l13puV0OVnoxsfTFDuZHzXt/5LHmCdI/URzPK3OAL83QlJtwKck1cLU6Ufywlhc=
=LBgn
-----END PGP SIGNATURE-----




  reply	other threads:[~2015-12-02  0:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 22:03 [PATCHv2] [layerindex-web] recipe blacklisted information Alex Franco
2015-11-30 22:22 ` Paul Eggleton
2015-11-30 22:42   ` strange QA issue - how to ignore automatic so dependency Dvorkin Dmitry
2015-11-30 23:06     ` Khem Raj
2015-11-30 23:15       ` Dvorkin Dmitry
2015-11-30 23:22         ` Khem Raj
2015-11-30 23:32           ` Dvorkin Dmitry
2015-12-01  9:40   ` [PATCHv2] [layerindex-web] recipe blacklisted information Martin Jansa
2015-12-01 10:42     ` Barros Pena, Belen
2015-12-01 11:14       ` Martin Jansa
     [not found]         ` <565DDB89.1030005@intel.com>
2015-12-01 18:26           ` Alex Franco
2015-12-01 19:11             ` Paul Eggleton
2015-12-02  0:47               ` Alex Franco [this message]
2015-12-02 11:38                 ` Barros Pena, Belen
2015-12-02 11:35               ` Barros Pena, Belen
2015-12-02 20:02                 ` Paul Eggleton

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=565E3F9F.7070609@linux.intel.com \
    --to=alejandro.franco@linux.intel.com \
    --cc=paul.eggleton@intel.com \
    --cc=yocto@yoctoproject.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.