summaryrefslogtreecommitdiff
path: root/README.cvs-commits
diff options
context:
space:
mode:
authorManish Singh <yosh@gimp.org>2005-01-27 22:26:04 +0000
committerManish Singh <yosh@src.gnome.org>2005-01-27 22:26:04 +0000
commit07155e27824a47fa89cb72d8c58bdcc3e15f6241 (patch)
treef9db3c897644f28eaf526af05e8c5f7d34ba2a89 /README.cvs-commits
parent9032abed7cacce3fd6467b9fef20c8bc9bda9a1a (diff)
downloadgtk+-07155e27824a47fa89cb72d8c58bdcc3e15f6241.tar.gz
update ancient IRC info.
Thu Jan 27 14:25:45 2005 Manish Singh <yosh@gimp.org> * README.cvs-commits: update ancient IRC info.
Diffstat (limited to 'README.cvs-commits')
-rw-r--r--README.cvs-commits8
1 files changed, 4 insertions, 4 deletions
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_.