Skip to contentSkip to conversation

] rrs/tools/rrs_upstream_email.py: Update message to point recipe file instead of deprecated upstream tracking file.

PATCH New Aníbal Limón 1 participant 1 message Jan 4, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ] rrs/tools/rrs_upstream_email.py: Update message to point recipe file instead of deprecated upstream tracking file.

Since upstream_tracking.inc file is deprecated because now every recipe has it's own upstream information then update email message according it.

---
 rrs/tools/rrs_upstream_email.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
rrs/tools/rrs_upstream_email.py +3 -3
index 3cde73b..a70ba13 100755
@@ -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:
 
Signature · 1 line
2.1.4