Paul Eggleton 2afa51b108 rrs_upgrade_history: only look at commits that actually change recipes ... Since we're now executing a separate script per commit, we should try not to do that unless the commit actually touches recipe files in order to avoid wasting time. (Whilst it's possible that a change to a bbclass might alter what's in the recipe, we can ignore that since we are only concerned with actual upgrades which would always require some sort of change to the recipe or an include file, so we can safely skip commits that don't do that.) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>		2018-05-04 23:57:53 +12:00
..
migrations	rrs_upgrade_history: use date/commit of last recipe upgrade import	2018-05-04 23:57:53 +12:00
static	rrs/base_toplevel.html: Navbar redesign	2018-05-04 23:57:52 +12:00
tools	rrs_upgrade_history: only look at commits that actually change recipes	2018-05-04 23:57:53 +12:00
__init__.py	rrs: show full name in admin	2018-05-04 23:57:52 +12:00
admin.py	rrs_upgrade_history: use date/commit of last recipe upgrade import	2018-05-04 23:57:53 +12:00
apps.py	rrs: show full name in admin	2018-05-04 23:57:52 +12:00
context_processors.py	rrs: Add application	2018-05-04 23:57:51 +12:00
models.py	rrs_upgrade_history: use date/commit of last recipe upgrade import	2018-05-04 23:57:53 +12:00
urls.py	Add link to maintenance plan in layer detail	2018-05-04 23:57:53 +12:00
views.py	rrs: add breadcrumb to recipe detail page	2018-05-04 23:57:53 +12:00
wsgi.py	rrs: Add wsgi file for serve with gunicorn	2018-05-04 23:57:52 +12:00