Paul Eggleton 7606664eeb rrs: link maintenance/upstream history to layerbranch ... RecipeUpstreamHistory was not linked to the layer it was produced from, which meant that it wasn't easy to query for a different maintenance plan (i.e. a different layer) and thus the maintenance plan selection on the recipe list didn't really work. Add a link field, populate it in a migration and then make it required. We had added a link earlier from RecipeMaintainerHistory to LayerBranch but it was optional; for the same reasons we now populate it and make it required. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>		2018-05-04 23:57:53 +12:00
..
common.py	rrs/tools: ensure recipe parsing code deletes temporary dir	2018-05-04 23:57:53 +12:00
daily_run.sh	rrs/tools/rrs_unique_recipes: drop	2018-05-04 23:57:52 +12:00
rrs_distros.py	rrs/tools: add -p/--plan option	2018-05-04 23:57:53 +12:00
rrs_maintainer_history.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
rrs_upgrade_history.py	rrs/tools: add -p/--plan option	2018-05-04 23:57:53 +12:00
rrs_upstream_email.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
rrs_upstream_history.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
upgrade_history_internal.py	rrs_upgrade_history: improve checkout logic	2018-05-04 23:57:53 +12:00