summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOwen Taylor <otaylor@redhat.com>2001-03-01 02:27:02 +0000
committerOwen Taylor <otaylor@src.gnome.org>2001-03-01 02:27:02 +0000
commit3cff4af6bea12c35b9bace4d1a5cd45ac94aaa54 (patch)
tree6dccc6368387d998fc7857177fc28c01a9cb4b9d
parentb2abe45d57a12707c3cd0633313a2e9c430d5193 (diff)
Propagate changes commited to the README.in back to here.GLIB_1_2_9PRE3
Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com> * README.in: Propagate changes commited to the README.in back to here.
-rw-r--r--ChangeLog5
-rw-r--r--ChangeLog.pre-2-05
-rw-r--r--ChangeLog.pre-2-105
-rw-r--r--ChangeLog.pre-2-125
-rw-r--r--ChangeLog.pre-2-25
-rw-r--r--ChangeLog.pre-2-45
-rw-r--r--ChangeLog.pre-2-65
-rw-r--r--ChangeLog.pre-2-85
-rw-r--r--README.in40
9 files changed, 62 insertions, 18 deletions
diff --git a/ChangeLog b/ChangeLog
index 5dae95c65..20e776db2 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/ChangeLog.pre-2-0 b/ChangeLog.pre-2-0
index 5dae95c65..20e776db2 100644
--- a/ChangeLog.pre-2-0
+++ b/ChangeLog.pre-2-0
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/ChangeLog.pre-2-10 b/ChangeLog.pre-2-10
index 5dae95c65..20e776db2 100644
--- a/ChangeLog.pre-2-10
+++ b/ChangeLog.pre-2-10
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/ChangeLog.pre-2-12 b/ChangeLog.pre-2-12
index 5dae95c65..20e776db2 100644
--- a/ChangeLog.pre-2-12
+++ b/ChangeLog.pre-2-12
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/ChangeLog.pre-2-2 b/ChangeLog.pre-2-2
index 5dae95c65..20e776db2 100644
--- a/ChangeLog.pre-2-2
+++ b/ChangeLog.pre-2-2
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/ChangeLog.pre-2-4 b/ChangeLog.pre-2-4
index 5dae95c65..20e776db2 100644
--- a/ChangeLog.pre-2-4
+++ b/ChangeLog.pre-2-4
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/ChangeLog.pre-2-6 b/ChangeLog.pre-2-6
index 5dae95c65..20e776db2 100644
--- a/ChangeLog.pre-2-6
+++ b/ChangeLog.pre-2-6
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/ChangeLog.pre-2-8 b/ChangeLog.pre-2-8
index 5dae95c65..20e776db2 100644
--- a/ChangeLog.pre-2-8
+++ b/ChangeLog.pre-2-8
@@ -1,3 +1,8 @@
+Wed Feb 28 21:26:18 2001 Owen Taylor <otaylor@redhat.com>
+
+ * README.in: Propagate changes commited to the README.in
+ back to here.
+
Wed Feb 28 16:59:05 2001 Owen Taylor <otaylor@redhat.com>
* configure.in (mem_warn): Add discouraging message if
diff --git a/README.in b/README.in
index c604414e4..2bf8d3c4b 100644
--- a/README.in
+++ b/README.in
@@ -11,11 +11,11 @@ The official ftp site is:
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
============
@@ -25,26 +25,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.
+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.
-In the mail include:
-
-* 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.
@@ -58,9 +55,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.)