GTK+ 1.2.10 with patches from several distributions.
C Shell Other
Switch branches/tags
Nothing to show
Permalink
Failed to load latest commit information.
docs Added missing gtkfaq-8 and gtkfaq-9 (from http://patch-tracker.debian… Feb 4, 2010
examples Recode ChangeLog and examples/calendar/calendar.c as UTF-8 Feb 4, 2010
gdk Import of gtk+-1.2.10-fontwarning.patch (from http://cvs.fedoraprojec… Feb 4, 2010
gtk gtkmenubar-noborder.patch (from http://cvs.mandriva.com/cgi-bin/viewv… Feb 4, 2010
intl Initial import Feb 4, 2010
po Initial import Feb 4, 2010
ABOUT-NLS Initial import Feb 4, 2010
AUTHORS Initial import Feb 4, 2010
COPYING Initial import Feb 4, 2010
ChangeLog Recode ChangeLog and examples/calendar/calendar.c as UTF-8 Feb 4, 2010
ChangeLog.pre-1-0 Initial import Feb 4, 2010
HACKING Initial import Feb 4, 2010
INSTALL Initial import Feb 4, 2010
Makefile.am Initial import Feb 4, 2010
Makefile.in Initial import Feb 4, 2010
NEWS Initial import Feb 4, 2010
NEWS.pre-1-0 Initial import Feb 4, 2010
README Initial import Feb 4, 2010
README.cvs-commits Initial import Feb 4, 2010
TODO Initial import Feb 4, 2010
acconfig.h From http://patch-tracker.debian.org/patch/misc/view/gtk+1.2/1.2.10-1… Feb 4, 2010
acinclude.m4 Initial import Feb 4, 2010
aclocal.m4 Import of gtk+-1.2.10-libtool.patch (from http://cvs.fedoraproject.or… Feb 4, 2010
config.guess Initial import Feb 4, 2010
config.h.in From http://patch-tracker.debian.org/patch/misc/view/gtk+1.2/1.2.10-1… Feb 4, 2010
config.sub Initial import Feb 4, 2010
configure Import of gtk+-1.2.10-libtool.patch (from http://cvs.fedoraproject.or… Feb 4, 2010
configure.in From http://patch-tracker.debian.org/patch/misc/view/gtk+1.2/1.2.10-1… Feb 4, 2010
gdk.pc.in Initial import Feb 4, 2010
gtk+.pc.in Initial import Feb 4, 2010
gtk+.spec Initial import Feb 4, 2010
gtk+.spec.in Initial import Feb 4, 2010
gtk-config.in Import of gtk+-1.2.10-multilib.patch (from http://cvs.fedoraproject.o… Feb 4, 2010
gtk.m4 Initial import Feb 4, 2010
install-sh Initial import Feb 4, 2010
ltconfig Import of gtk+-1.2.10-ppc64.patch (from http://cvs.fedoraproject.org/… Feb 4, 2010
ltmain.sh Initial import Feb 4, 2010
makecopyright Initial import Feb 4, 2010
missing Initial import Feb 4, 2010
mkinstalldirs Initial import Feb 4, 2010
stamp-h.in Initial import Feb 4, 2010

README

General Information
===================

This is GTK+ version 1.2.10. 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.

The official ftp site is:
  ftp://ftp.gtk.org/pub/gtk

The official web site is:
  http://www.gtk.org/

Information about mailing lists can be found at
  http://www.gtk.org/mailinglists.html

Installation
============

See the file 'INSTALL'

How to report bugs
==================

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

* If the bug was a crash, the exact text that was printed out
  when the crash occured.

* Further information such as stack traces may be useful, but
  is not necessary. If you do send a stack trace, and the error
  is an X error, it will be more useful if the stacktrace
  is produced running the test program with the --sync command
  line option.

Patches
=======

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 GTK
programming interface, the API keyword should also be included.
  
Patches should be in unified diff form. (The -u option to GNU
diff.)