diff --git a/ChangeLog b/ChangeLog
index ad525a6ded..2a0c90431b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+Thu Jan 27 14:25:45 2005  Manish Singh  <yosh@gimp.org>
+
+	* README.cvs-commits: update ancient IRC info.
+
 2005-01-27  Federico Mena Quintero  <federico@ximian.com>
 
 	Merged from gtk-2-6:
diff --git a/ChangeLog.pre-2-10 b/ChangeLog.pre-2-10
index ad525a6ded..2a0c90431b 100644
--- a/ChangeLog.pre-2-10
+++ b/ChangeLog.pre-2-10
@@ -1,3 +1,7 @@
+Thu Jan 27 14:25:45 2005  Manish Singh  <yosh@gimp.org>
+
+	* README.cvs-commits: update ancient IRC info.
+
 2005-01-27  Federico Mena Quintero  <federico@ximian.com>
 
 	Merged from gtk-2-6:
diff --git a/ChangeLog.pre-2-8 b/ChangeLog.pre-2-8
index ad525a6ded..2a0c90431b 100644
--- a/ChangeLog.pre-2-8
+++ b/ChangeLog.pre-2-8
@@ -1,3 +1,7 @@
+Thu Jan 27 14:25:45 2005  Manish Singh  <yosh@gimp.org>
+
+	* README.cvs-commits: update ancient IRC info.
+
 2005-01-27  Federico Mena Quintero  <federico@ximian.com>
 
 	Merged from gtk-2-6:
diff --git a/README.cvs-commits b/README.cvs-commits
index ecf64a4b0f..097aa9e6b2 100644
--- a/README.cvs-commits
+++ b/README.cvs-commits
@@ -18,10 +18,10 @@ to ask people commiting to GTK+ to follow a few rules:
    gtk-devel-list-request@gnome.org.) This is a good place to ask
    about intended changes. 
 
-   #gimp on byxnet (irc.gimp.org, irc2.gimp.org, irc3.gimp.org, 
-   irc.germany.gimp.org...)s also a good place to find GTK+ developers to
-   discuss changes with, however, email to gtk-devel-list is the most
-   certain and preferred method.
+   #gtk+ on GIMPNet (irc.gimp.org, irc.us.gimp.org, irc.eu.gimp.org, ...)
+   is also a good place to find GTK+ developers to discuss changes with,
+   however, email to gtk-devel-list is the most certain and preferred
+   method.
 
 1) Ask _first_.