From: Martin Jansa <martin.jansa@gmail.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Franco, Alejandro" <alejandro.franco@intel.com>,
"Eggleton, Paul" <paul.eggleton@intel.com>
Subject: Re: [PATCHv2] [layerindex-web] recipe blacklisted information
Date: Tue, 1 Dec 2015 12:14:51 +0100 [thread overview]
Message-ID: <20151201111451.GC2251@jama> (raw)
In-Reply-To: <D2832681.6BDCB%belen.barros.pena@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
On Tue, Dec 01, 2015 at 10:42:49AM +0000, Barros Pena, Belen wrote:
>
>
> On 01/12/2015 09:40, "yocto-bounces@yoctoproject.org on behalf of Martin
> Jansa" <yocto-bounces@yoctoproject.org on behalf of
> martin.jansa@gmail.com> wrote:
>
> >>Another thing that just occurred to me though - apologies for not
> >>raising it
> >>earlier - for the benefit of newer users it may be useful to explain
> >>implications of the blacklisting. What I'd suggest is we put a line
> >>after the
> >>reason on the recipe detail page saying "This means that the recipe will
> >>not
> >>be buildable until the PNBLACKLIST value is cleared and the issue that
> >>caused
> >>it to be added has been fixed or worked around." (Just on the recipe
> >>detail
> >>page - not in the popup.)
> >>Does that sound OK?
> >
> >Maybe some more information how to clear PNBLACKLIST (people often don't
> >know that they can just set it to empty value in their bbappend or even
> >distro/local config).
>
> I think explaining what blacklisting means, its implications and how to
> clear it is an excellent idea, but it seems there is quite a lot to say,
> and the layer index itself might not be the best place to show it all. So
> what about adding all this to the documentation, then link to it from the
> layer index? The recipe details page would then look like the attached
> image.
Agreed, LGTM.
>
> Alex, sorry for nitpicking: using the .label-inverse class means that the
> label in the h1 of the recipe details page also hovers. Only labels with a
> tooltip should hover, so maybe we should go back to the extra class, or
> just qualify the hover styles so that they only apply to .label-inverse
> inside tables (td > .label-inverse:hover). Apologies: I should have picked
> this up before you submitted the patch.
>
> Cheers
>
> Belén
>
> >
> >--
> >Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-12-01 11:13 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 [this message]
[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
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=20151201111451.GC2251@jama \
--to=martin.jansa@gmail.com \
--cc=alejandro.franco@intel.com \
--cc=belen.barros.pena@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.