X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=README;h=151e3c8ca5bb2cd6afdc7f7b3d85821ec01d9df1;hb=2c396fea9f4b183f5a2739a9ebc5076b0374d225;hp=e1a7b9564f47d2580c84cc25e31d801004027a18;hpb=4848d691e00a1cfe4dd6af55b6b74b7f208c605d;p=~andy%2Fgtk diff --git a/README b/README index e1a7b9564..151e3c8ca 100644 --- a/README +++ b/README @@ -1,7 +1,7 @@ General Information =================== -This is GTK+ version 1.1.3. GTK+, which stands for the Gimp ToolKit, +This is GTK+ version 1.3.5. GTK+, which stands for the Gimp ToolKit, is a library for creating graphical user interfaces for the X Window System. It is designed to be small, efficient, and flexible. GTK+ is written in C with a very object-oriented approach. @@ -12,11 +12,8 @@ The official ftp site is: The official web site is: http://www.gtk.org/ -A mailing list is located at: - gtk-list@redhat.com - -To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null -(Send mail to gtk-list-request@redhat.com with the subject "subscribe") +Information about mailing lists can be found at + http://www.gtk.org/mailinglists.html Installation ============ @@ -26,14 +23,12 @@ 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: - -* The version of GTK - +Bugs should be reported to the GNOME bug tracking system. +(http://bugzilla.gnome.org, product gtk+.) You will need +to create an account for yourself. + +In the bug report please include: + * Information about your system. For instance: - What operating system and version @@ -50,11 +45,6 @@ In the mail include: As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded. - (Bugs that can be reproduced within the GIMP are almost as good - as bugs that can be reproduced in testgtk. If you are reporting a - bug found with the GIMP, please include the version number of the GIMP - you are using) - * If the bug was a crash, the exact text that was printed out when the crash occured. @@ -67,9 +57,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. -If the patch fixes a bug, it is usually a good idea to include -all the information described in "How to Report Bugs". +Bug reports containing patches should include the PATCH keyword +in their keyword fields. If the patch adds to or changes the GTK +programming interface, the API keyword should also be included. + +Patches should be in unified diff form. (The -u option to GNU +diff.)