All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: [layerindex-web][PATCH 3/3] Show note if layer branch hasn't been indexed
Date: Wed,  4 Oct 2017 13:51:03 +1300	[thread overview]
Message-ID: <20171004005103.24756-3-paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <20171004005103.24756-1-paul.eggleton@linux.intel.com>

For newly added layers it may not be immediately obvious that you have
to wait for it to be indexed (since the update script is usually run on
a scheduled basis). If the layer branch hasn't been indexed, add a note
mentioning this.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
 templates/layerindex/detail.html | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/templates/layerindex/detail.html b/templates/layerindex/detail.html
index 144d5e8..0747421 100644
--- a/templates/layerindex/detail.html
+++ b/templates/layerindex/detail.html
@@ -167,6 +167,11 @@
             </div>  <!-- end of row-fluid -->
         </div> <!-- end of container-fluid -->
 
+        {% if not layerbranch.vcs_last_commit %}
+        <div class="alert alert-info">
+            <b>Note:</b> The content of this layer on branch {{ url_branch }} has not yet been indexed. Indexing should take place within a few hours.
+        </div>
+        {% endif %}
 
         <ul class="nav nav-tabs" id="layertabbar">
             {% if layerbranch.recipe_set.count > 0 %}
-- 
2.9.5



      parent reply	other threads:[~2017-10-04  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  0:51 [layerindex-web][PATCH 1/3] update: allow preserving temp directory Paul Eggleton
2017-10-04  0:51 ` [layerindex-web][PATCH 2/3] models: allow LayerBranch.collection to be blank Paul Eggleton
2017-10-04  0:51 ` Paul Eggleton [this message]

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=20171004005103.24756-3-paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.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.