AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity

update ancient IRC info.

Browse Source 
Thu Jan 27 14:25:45 2005  Manish Singh  <yosh@gimp.org>

        * README.cvs-commits: update ancient IRC info.
This commit is contained in:
Manish Singh 2005-01-27 22:26:04 +00:00 committed by Manish Singh
parent 9032abed7c
commit 07155e2782
4 changed files with 16 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -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:

4
ChangeLog.pre-2-10
View File

@ -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:

4
ChangeLog.pre-2-8
View File

@ -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:

8
README.cvs-commits
View File

@ -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_.