From 8ea5efe03483bb28771dee34ba45aea556699551 Mon Sep 17 00:00:00 2001
From: Sergio Durigan Junior <sergiodj@redhat.com>
Date: Thu, 28 Sep 2017 14:25:05 -0400
Subject: [PATCH] s/SendAuthorMessage/SendAuthorBreakageMessage/

---
 master.cfg | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/master.cfg b/master.cfg
index 68ce93a..db5ec63 100644
--- a/master.cfg
+++ b/master.cfg
@@ -219,7 +219,7 @@ def SendRootMessageGDBTesters (branch, change, rev,
 def make_breakage_lockfile_name (branch, builder):
     return "/tmp/gdb-buildbot-breakage-report-%s-%s" % (branch, builder)
 
-def SendAuthorMessage (name, branch, change, text_prepend):
+def SendAuthorBreakageMessage (name, branch, change, text_prepend):
     """Send a message to the author of the commit if it broke GDB.
 
 We use a lock file to avoid reporting the breakage to different
@@ -423,7 +423,7 @@ send to the gdb-testers mailing list."""
 
     if report_build_breakage:
         subj += " *** BREAKAGE ***"
-        SendAuthorMessage (name, branch, cur_change, text)
+        SendAuthorBreakageMessage (name, branch, cur_change, text)
     else:
         # There is no build breakage anymore!  Yay!  Now, let's see if
         # we need to clean up any lock file from previous breaks.