include glib-object.h rather than gobject/gobject.h

[platform/upstream/glib.git] / README

diff --git a/README b/README
index 1f417cb..13d62f5 100644 (file)
--- a/README
+++ b/README
@@ -1,24 +1,33 @@
+ *** IMPORTANT *** 
+
+This is a development version of GLib.  You should be using a stable
+version, which is available at ftp://ftp.gtk.org/pub/gtk/v1.2/.  This
+version is meant for developers of GLib only:
+
+ * You should not base stable software on this version of GLib.
+ * GNOME developers should use a stable version of GLib.
+
+*** You should be using GLib 1.2 instead. ***
+
+
 General Information
 ===================
 
-This is GLib version 1.1.12. GLib, is a library which includes support
+This is GLib version 1.3.10. GLib is a library which includes support
 routines for C such as lists, trees, hashes, memory allocation, and
 many other things.
 
-Versions of GLib prior to 1.1.0 are distributed with GTK+ versions prior
-to 1.1.0.
-
 The official ftp site is:
   ftp://ftp.gtk.org/pub/gtk
 
 The official web site is:
   http://www.gtk.org/
 
-A mailing list is located at:
-  gtk-list@redhat.com
+Information about mailing lists can be found at
+  http://www.gtk.org/mailinglists.html
 
-To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null
-(Send mail to gtk-list-request@redhat.com with the subject "subscribe")
+To subscribe: mail -s subscribe gtk-list-request@gnome.org < /dev/null
+(Send mail to gtk-list-request@gnome.org with the subject "subscribe")
 
 Installation
 ============
@@ -28,26 +37,23 @@ See the file 'INSTALL'
 How to report bugs
 ==================
 
-To report a bug, send mail either to gtk-list, as mentioned
-above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you
-must be subscribed yourself.
-
-In the mail include:
+Bugs should be reported to the GNOME bug tracking system. 
+(http://bugzilla.gnome.org, product glib.) You will need
+to create an account for yourself.
 
-* The version of GLib
+In the bug report please include:
 
 * Information about your system. For instance:
 
    - What operating system and version
-   - What version of X
    - For Linux, what version of the C library
 
   And anything else you think is relevant.
 
 * How to reproduce the bug. 
 
-  If you can reproduce it with the testglib program that is built 
-  in the glib/ directory, that will be most convenient.  Otherwise, 
+  If you can reproduce it with the testgtk program that is built 
+  in the gtk/ subdirectory, that will be most convenient.  Otherwise, 
   please include a short test program that exhibits the behavior. 
   As a last resort, you can also provide a pointer to a larger piece 
   of software that can be downloaded.
@@ -61,9 +67,16 @@ In the mail include:
 Patches
 =======
 
-Patches can be uploaded to the incoming/ directory on
-ftp.gtk.org.  Please follow the instructions there, and include
-your name and email address in the README file.
+Patches should also be submitted to bugzilla.gnome.org. If the
+patch fixes an existing bug, add the patch as an attachment
+to that bug report.
+
+Otherwise, enter a new bug report that describes the patch,
+and attach the patch to that bug report.
+
+Bug reports containing patches should include the PATCH keyword
+in their keyword fields. If the patch adds to or changes the GLib 
+programming interface, the API keyword should also be included.
 
-If the patch fixes a bug, it is usually a good idea to include
-all the information described in "How to Report Bugs".
+Patches should be in unified diff form. (The -u option to GNU
+diff.)