summaryrefslogtreecommitdiff
path: root/README.cvs-commits
diff options
context:
space:
mode:
authorOwen Taylor <otaylor@redhat.com>2001-04-17 19:19:09 +0000
committerOwen Taylor <otaylor@src.gnome.org>2001-04-17 19:19:09 +0000
commiteced7172800dd6a5ec5cd5dfca15c4eb80e4b915 (patch)
treee55bdef263bc1b01d8d9cdf59161094ba4c7685b /README.cvs-commits
parentca2a67b4c6fbed8d99559ab68326f866bb472a89 (diff)
downloadgtk+-eced7172800dd6a5ec5cd5dfca15c4eb80e4b915.tar.gz
Don't put -lgthread in GLIB_LIBS, GLIB_DEPLIBS
Tue Apr 17 13:47:12 2001 Owen Taylor <otaylor@redhat.com> * configure.in: Don't put -lgthread in GLIB_LIBS, GLIB_DEPLIBS * gtk/gtktypeutils.h gtk/gtksignals.h: Restore proper parameter names to compatibility #defines so docs work. * gtk/gtkenums.h: Remove GtkMenuFactoryType * gtk/gtkwindow.c gtk/gtkdnd.c: Docs cleanups. * configure.in: Don't include -lgthread in GLIB_LIBS, GLIB_DEPLIBS * tests/testgtkrc: No magenta cursors, please. * README.in INSTALL.in HACKING README.cvs-commits: Updated. * gtk/gtkenums.h (enum): Remove left over GtkMenuFactoryType.
Diffstat (limited to 'README.cvs-commits')
-rw-r--r--README.cvs-commits17
1 files changed, 4 insertions, 13 deletions
diff --git a/README.cvs-commits b/README.cvs-commits
index 12231d72b6..ecf64a4b0f 100644
--- a/README.cvs-commits
+++ b/README.cvs-commits
@@ -4,7 +4,7 @@ GTK+. This is a good thing, in that it encourages many people to work
on GTK+, and progress can be made quickly. However, GTK+ is a fairly
large and complicated package that many other things depend on, so to
avoid unnecessary breakage, and to take advantage of the knowledge
-about GTK+ that has been built up over the last 18 months, we'd like
+about GTK+ that has been built up over the last 4 years, we'd like
to ask people commiting to GTK+ to follow a few rules:
0) Ask first. If your changes are major, or could possibly break existing
@@ -14,15 +14,10 @@ to ask people commiting to GTK+ to follow a few rules:
somebody may know a better way to do things.
If you are making changes to GTK+, you should be subscribed
- to gtk-devel-list@redhat.com. (Subscription address:
- gtk-devel-list-request@redhat.com.) This is a good place to ask
+ to gtk-devel-list@gnome.org. (Subscription address:
+ gtk-devel-list-request@gnome.org.) This is a good place to ask
about intended changes.
- If you just want to make a trivial change, and don't want to subscribe,
- you can also mail gtk-bugs@gtk.org. Or, alternatively, you can look in
- the ChangeLog for somebody who has been making changes to the file
- you want to change and email them.
-
#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
@@ -56,8 +51,4 @@ Notes:
Owen Taylor
13 Aug 1998
-
-
-
-
-
+17 Apr 2001