From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: [layerindex-web][PATCH 0/7] Recipe reporting system fixes (cover letter only)
Date: Wed, 17 Jul 2019 11:41:25 +1200 [thread overview]
Message-ID: <cover.1563320190.git.paul.eggleton@linux.intel.com> (raw)
A bunch of fixes mostly for the Recipe Reporting System (RRS) part of
the layer index. In particular, 5/7 fixes the RRS for layers in
meta-openembedded.
The following changes since commit ce5141fc39b2b171383fca002b2bc5cf082b31f4:
RRS: add tool to import/export upstream history data (2019-02-14 10:05:53 +1300)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/fixes13
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/fixes13
Paul Eggleton (7):
Split out patch status read to a method on the Patch model
Record patch application order and use as default sorting
Add admin handling for Patch objects
RRS: Fix raw SQL statements to use parameters
RRS: fix showing all recipes for multi-layer maintenance plans
RRS: move Export button and restore Tools drop-down menu
RRS: add missing migration
layerindex/admin.py | 11 +-
.../migrations/0027_patch_apply_order.py | 24 +++
layerindex/models.py | 31 ++++
layerindex/tools/import_otherdistro.py | 5 +-
layerindex/update_layer.py | 34 +----
.../0019_maintplan_admin_delete_null.py | 22 +++
rrs/views.py | 143 +++++++++---------
templates/base.html | 4 +
templates/rrs/base_toplevel.html | 5 +-
templates/rrs/recipes.html | 2 +
10 files changed, 173 insertions(+), 108 deletions(-)
create mode 100644 layerindex/migrations/0027_patch_apply_order.py
create mode 100644 rrs/migrations/0019_maintplan_admin_delete_null.py
--
2.20.1
reply other threads:[~2019-07-16 23:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1563320190.git.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.