From 2943d182e5ac5d12b7d4ca51bbdf98a65e37e0f7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?An=C3=ADbal=20Lim=C3=B3n?= Date: Mon, 4 Jan 2016 14:17:00 -0600 Subject: [PATCH] rrs/tools/rrs_upstream_email.py: Update message to point recipe file instead of deprecated upstream tracking file. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- rrs/tools/rrs_upstream_email.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/rrs/tools/rrs_upstream_email.py b/rrs/tools/rrs_upstream_email.py index 3cde73b..0e73957 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 -recipe remainder until newer upstream version was detected. +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 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 = "Version 2.0 is unstable" You can check the detail information at: