4 This is GLib version @GLIB_VERSION@. GLib is the low-level core
5 library that forms the basis for projects such as GTK+ and GNOME. It
6 provides data structure handling for C, portability wrappers, and
7 interfaces for such runtime functionality as an event loop, threads,
8 dynamic loading, and an object system.
10 The official ftp site is:
11 ftp://ftp.gtk.org/pub/gtk
13 The official web site is:
16 Information about mailing lists can be found at
17 http://www.gtk.org/mailinglists.html
19 To subscribe: mail -s subscribe gtk-list-request@gnome.org < /dev/null
20 (Send mail to gtk-list-request@gnome.org with the subject "subscribe")
25 See the file 'INSTALL'
30 Bugs should be reported to the GNOME bug tracking system.
31 (http://bugzilla.gnome.org, product glib.) You will need
32 to create an account for yourself.
34 In the bug report please include:
36 * Information about your system. For instance:
38 - What operating system and version
39 - For Linux, what version of the C library
41 And anything else you think is relevant.
43 * How to reproduce the bug.
45 If you can reproduce it with the testgtk program that is built
46 in the gtk/ subdirectory, that will be most convenient. Otherwise,
47 please include a short test program that exhibits the behavior.
48 As a last resort, you can also provide a pointer to a larger piece
49 of software that can be downloaded.
51 * If the bug was a crash, the exact text that was printed out
52 when the crash occured.
54 * Further information such as stack traces may be useful, but
60 Patches should also be submitted to bugzilla.gnome.org. If the
61 patch fixes an existing bug, add the patch as an attachment
64 Otherwise, enter a new bug report that describes the patch,
65 and attach the patch to that bug report.
67 Bug reports containing patches should include the PATCH keyword
68 in their keyword fields. If the patch adds to or changes the GLib
69 programming interface, the API keyword should also be included.
71 Patches should be in unified diff form. (The -u option to GNU