(GDB/MI Development and Front Ends): Use sourceware.org for mailing lists.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 4895d7e4f27bba7ad6c64016d2a847eaa58617cb..a0e4df84c5ba5a341881e5bc039656b6bd67d9ee 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -17616,8 +17616,8 @@ responsibility of the front end to work with the new one.
 
 The best way to avoid unexpected changes in MI that might break your front
 end is to make your project known to @value{GDBN} developers and
-follow development on @email{gdb@@sources.redhat.com} and
-@email{gdb-patches@@sources.redhat.com}.  There is also the mailing list
+follow development on @email{gdb@@sourceware.org} and
+@email{gdb-patches@@sourceware.org}.  There is also the mailing list
 @email{dmi-discuss@@lists.freestandards.org}, hosted by the Free Standards
 Group, which has the aim of creating a a more general MI protocol
 called Debugger Machine Interface (DMI) that will become a standard