Since upstream_tracking.inc file is deprecated because now every recipe has it's own upstream information then update email message according it.
Signed-off-by: Aníbal Limón <anibal.li...@linux.intel.com> --- rrs/tools/rrs_upstream_email.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rrs/tools/rrs_upstream_email.py b/rrs/tools/rrs_upstream_email.py index 3cde73b..a70ba13 100755 --- a/rrs/tools/rrs_upstream_email.py +++ b/rrs/tools/rrs_upstream_email.py @@ -38,12 +38,12 @@ def send_email(recipes, repodir, options): header = """This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers -believe some of them needn't to upgrade this time, they can fill in -RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this +believe some of them needn't to upgrade at this time, they can fill +RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this recipe recipe remainder until newer upstream version was detected. Example: -RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 is unstable" +RECIPE_NO_UPDATE_REASON = "Not upgrade to 2.0 is unstable" You can check the detail information at: -- 2.1.4 -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto