From 4b733996b23cbbd19a261c6435ad86a8a545fec9 Mon Sep 17 00:00:00 2001 From: Andrew Hutchings Date: Mon, 14 May 2012 17:27:50 +0100 Subject: [PATCH] Change expire messages From Jim: "I think the confusion may be coming from people who only see this message via email. In that case, indicating that the button is available in the web UI when visiting the change may be helpful." Done! Change-Id: I1125cfc5040b6351ef956527b90e71f4d33f30a0 --- expire_old_reviews.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/expire_old_reviews.py b/expire_old_reviews.py index f379eac..89686c8 100644 --- a/expire_old_reviews.py +++ b/expire_old_reviews.py @@ -40,9 +40,9 @@ ssh.connect('localhost', username=GERRIT_USER, key_filename=GERRIT_SSH_KEY, port def expire_patch_set(patch_id, patch_subject, has_negative): if has_negative: - message= 'code review expired after 1 week of no activity after a negative review, it can be restored using the \`Restore Change\` button above' + message= 'code review expired after 1 week of no activity after a negative review, it can be restored using the \`Restore Change\` button under the Patch Set on the web interface' else: - message= 'code review expired after 2 weeks of no activity, it can be restored using the \`Restore Change\` button above' + message= 'code review expired after 2 weeks of no activity, it can be restored using the \`Restore Change\` button under the Patch Set on the web interface' command='gerrit review --abandon --message="{0}" {1}'.format(message, patch_id) logger.info('Expiring: %s - %s: %s', patch_id, patch_subject, message) stdin, stdout, stderr = ssh.exec_command(command)