aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorNick Roberts <nickrob@snap.net.nz>2006-06-01 23:40:50 +0000
committerNick Roberts <nickrob@snap.net.nz>2006-06-01 23:40:50 +0000
commit7a9a6b69e4f3484e1ea5db3f1cdf279e3af9b4eb (patch)
treea04c71d5cb08d5626d4bafc39134f4b951520b53 /gdb/doc
parent2aef0d6badecf186ec2a90df16280fa7d287e797 (diff)
downloadgdb-7a9a6b69e4f3484e1ea5db3f1cdf279e3af9b4eb.zip
gdb-7a9a6b69e4f3484e1ea5db3f1cdf279e3af9b4eb.tar.gz
gdb-7a9a6b69e4f3484e1ea5db3f1cdf279e3af9b4eb.tar.bz2
(GDB/MI Development and Front Ends): Use sourceware.org for mailing lists.
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/gdb.texinfo4
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 4895d7e..a0e4df8 100644
--- 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