luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-23 18:52:09 +01:00
Code Issues Packages Projects Releases Wiki Activity

Propagate changes commited to the README.in back to here.

Browse Source 
Wed Feb 28 21:26:18 2001  Owen Taylor  <otaylor@redhat.com>

	* README.in: Propagate changes commited to the README.in
	back to here.
This commit is contained in:
Owen Taylor 2001-03-01 02:27:02 +00:00 committed by Owen Taylor
parent b2abe45d57
commit 3cff4af6be
9 changed files with 62 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -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

5
ChangeLog.pre-2-0
View File

@ -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

5
ChangeLog.pre-2-10
View File

@ -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

5
ChangeLog.pre-2-12
View File

@ -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

5
ChangeLog.pre-2-2
View File

@ -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

5
ChangeLog.pre-2-4
View File

@ -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

5
ChangeLog.pre-2-6
View File

@ -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

5
ChangeLog.pre-2-8
View File

@ -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

40
README.in
View File

@ -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.
If the patch fixes a bug, it is usually a good idea to include
all the information described in "How to Report Bugs".
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.
Patches should be in unified diff form. (The -u option to GNU
diff.)