From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: [layerindex-web][PATCH 0/3] Branch comparison functionality
Date: Mon, 21 Oct 2019 11:49:49 +1300 [thread overview]
Message-ID: <cover.1571611698.git.paul.eggleton@linux.intel.com> (raw)
Add the ability to compare the available recipes and their versions in
two different branches, plus one unrelated patch to fix an issue I
noticed recently with cgit URLs.
The following changes since commit 1ce4a85d257ac928307ac0de6edf4cb80b50adce:
editlayer: Be more specific on the searches (2019-10-14 09:20:33 +1300)
are available in the Git repository at:
git://git.yoctoproject.org/layerindex-web paule/branch_comparison
http://git.yoctoproject.org/cgit.cgi/layerindex-web/log/?h=paule/branch_comparison
Paul Eggleton (3):
Track SRCREV for each recipe
Add branch comparison function
Fix cgit commit URL setting
layerindex/forms.py | 19 ++
layerindex/migrations/0043_recipe_srcrev.py | 20 ++
layerindex/models.py | 1 +
layerindex/update_layer.py | 4 +
layerindex/urls.py | 12 +-
layerindex/views.py | 113 +++++++++-
templates/base.html | 1 +
templates/layerindex/branchcompare.html | 214 +++++++++++++++++++
templates/layerindex/branchcompare_plain.txt | 17 ++
templates/layerindex/editlayer.html | 2 +-
templates/layerindex/recipedetail.html | 2 +-
11 files changed, 401 insertions(+), 4 deletions(-)
create mode 100644 layerindex/migrations/0043_recipe_srcrev.py
create mode 100644 templates/layerindex/branchcompare.html
create mode 100644 templates/layerindex/branchcompare_plain.txt
--
2.20.1
next reply other threads:[~2019-10-20 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 22:49 Paul Eggleton [this message]
2019-10-20 22:49 ` [layerindex-web][PATCH 1/3] Track SRCREV for each recipe Paul Eggleton
2019-10-20 22:49 ` [layerindex-web][PATCH 2/3] Add branch comparison function Paul Eggleton
2019-10-20 22:49 ` [layerindex-web][PATCH 3/3] Fix cgit commit URL setting 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=cover.1571611698.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.