Paul Eggleton 20a420ec9c RRS: handle when recipes get deleted and later re-added ... We need to capture the re-addition properly or the recipe simply won't show up in the recipe list. Examples from meta-oe: * psqlodbc removed in ec9e5ed06256ad92c818474cdb490dc0d3a0d0a3 and added back in 16a6fee6c0455863ed5df15afc49efe8cc617d9c * libgxim removed in 5dd01c5175f518658d8ee5627ede4f593111b872 and added back in af602920594a9cc2e9b397fe311fda7f531be7f3 Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>		2019-11-21 02:27:39 +13:00
..
common.py	update: fix error on LAYERRECOMMENDS failure	2018-10-01 11:43:52 +13:00
daily_run.sh	rrs/tools/daily_run.sh: don't reload when updating	2018-09-06 11:08:43 +12:00
historytool.py	RRS: add tool to import/export upstream history data	2019-02-14 10:05:53 +13:00
rrs_distros.py	Use try...finally or with to ensure files get closed	2019-02-14 10:05:53 +13:00
rrs_maintainer_history.py	RRS: collect history independent of current recipes	2019-11-21 02:27:39 +13:00
rrs_upgrade_history.py	RRS: avoid historical parsing bug in bitbake	2019-11-21 02:27:39 +13:00
rrs_upstream_email.py	Use shell=False where possible with utils.runcmd()	2019-07-17 11:31:01 +12:00
rrs_upstream_history.py	RRS: collect history independent of current recipes	2019-11-21 02:27:39 +13:00
upgrade_history_internal.py	RRS: handle when recipes get deleted and later re-added	2019-11-21 02:27:39 +13:00