diff options
| author | Owen Taylor <otaylor@redhat.com> | 2001-04-17 19:19:09 +0000 |
|---|---|---|
| committer | Owen Taylor <otaylor@src.gnome.org> | 2001-04-17 19:19:09 +0000 |
| commit | eced7172800dd6a5ec5cd5dfca15c4eb80e4b915 (patch) | |
| tree | e55bdef263bc1b01d8d9cdf59161094ba4c7685b /HACKING | |
| parent | ca2a67b4c6fbed8d99559ab68326f866bb472a89 (diff) | |
| download | gtk+-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 'HACKING')
| -rw-r--r-- | HACKING | 19 |
1 files changed, 9 insertions, 10 deletions
@@ -41,16 +41,15 @@ to autogen.sh and they will be passed on to configure. If at all possible, please use CVS to get the latest development version of gtk+ and glib. You can do the following to get glib and gtk+ from cvs: - $ export CVSROOT=':pserver:anonymous@cvs.gimp.org:/debian/home/gnomecvs' + $ export CVSROOT=':pserver:anonymous@cvs.gnome.org:/cvs/gnome' $ cvs login (there is no password, just hit return) - $ cvs -z9 checkout glib - $ cvs -z9 checkout gtk+ - -Please submit patches to the gtk-list@redhat.com mailing list (you must -subscribe before you post, e-mail gtk-list-request@redhat.com with a -subject of "subscribe"). All kinds of contributions are accepted. -Patches that you wish to go into the distribution should also be uploaded -to ftp://ftp.gimp.org/incoming. Follow the rules there for naming your -patches. + $ cvs -z3 checkout glib + $ cvs -z3 checkout gtk+ + +For information about submitting patches and commiting changes +to CVS, see the README and README.cvs-commits files. In particular, +don't, under any circumstances, commit anything to CVS before +reading and understanding README.cvs-commmits. + |