Skip to content
Low-level core library that forms the basis for GTK+ and GNOME http://www.gtk.org/
C Other
Find file
Latest commit abfef39 @fanc999 fanc999 Remove uneeded item form VS10 folder
There is no install.vcxproj.filters...oops
Failed to load latest commit information.
build Remove uneeded item form VS10 folder
debian add -b (binary-only; no source packages) flag to dpkg-buildpackage
docs Allow to list keys in all schemas
gio Allow to list keys in all schemas
glib Bug 638185 - GIOCondition should be annotated as "flags"
gmodule Recuce DLL hijack risk on Windows
gobject Visual C++ 2010 Project Files: autotools files
gthread Remove the dead --disable-visiblity configure option
m4macros Fix gsettings enum rule to work with non-srcdir builds
po Updated Bulgarian translation
tests Update Unicode tests to 6.0
.gitignore move glibconfig.h to glib/
AUTHORS Updates
COPYING version bump to 1.1.1, binary age 1, interface age 0. updates. updates.
ChangeLog.pre-1-2 Fix typos: invokation -> invocation.
ChangeLog.pre-2-0 Fix typos: invokation -> invocation.
ChangeLog.pre-2-10 Adjust docs
ChangeLog.pre-2-12 Branch for 2.12
ChangeLog.pre-2-14 Added missing ChangeLog
ChangeLog.pre-2-16 Rotate ChangeLog
ChangeLog.pre-2-18 Bump version to 2.19.0
ChangeLog.pre-2-2 Split ChangeLog
ChangeLog.pre-2-20 Rename ChangeLog to ChangeLog.pre-2-20
ChangeLog.pre-2-4 Move aside ChangeLog for 2.4
ChangeLog.pre-2-6 Split ChangeLog for 2.6
ChangeLog.pre-2-8 Truncate ChangeLog after moving aside
HACKING Update README files to refer to git
INSTALL.in docs: Update the URL of some documentation links
MAINTAINERS Update file format
Makefile.am Clean autotools config a bit
Makefile.decl test: Add a <revision> node to the report XML
NEWS Updates
NEWS.pre-1-3 updates.
README.commits Update README files to refer to git
README.in Add release note about GApplication
README.win32 rename configure.in to configure.ac
acglib.m4 Update GLIB_CHECK_COMPILE_WARNINGS macro to work with Autoconf 2.64
acinclude.m4 Move some inter-*.m4 includes from configure.in to acinclude.m4 to avoid
autogen.sh allow libtool 2.4
config.h.win32.in rename configure.in to configure.ac
configure.ac Visual C++ 2010 Project Files: autotools files
gio-2.0-uninstalled.pc.in Require glib-2.0
gio-2.0.pc.in Append .exe to glib-compile-schemas in .pc file
gio-unix-2.0-uninstalled.pc.in gio/ docs/reference/gio Merged gio-standalone into glib.
gio-unix-2.0.pc.in gio/ docs/reference/gio Merged gio-standalone into glib.
gio-windows-2.0.pc.in Add GWin32InputStream and GWin32OutputStream classes
glib-2.0-uninstalled.pc.in Bug 534319 - GLib's .pc files could use Libs.private
glib-2.0.pc.in Bug 534319 - GLib's .pc files could use Libs.private
glib-gettextize.in Silence autoconf warnings about datarootdir. (#391367, Loïc Minier)
glib-zip.in Add GWin32InputStream and GWin32OutputStream classes
gmodule-2.0-uninstalled.pc.in Bug 600141 - Add -pthread to gmodule pkg-config
gmodule-2.0.pc.in Bug 600141 - Add -pthread to gmodule pkg-config
gmodule-export-2.0.pc.in Bug 600141 - Add -pthread to gmodule pkg-config
gmodule-no-export-2.0-uninstalled.pc.in Bug 600141 - Add -pthread to gmodule pkg-config
gmodule-no-export-2.0.pc.in Bug 600141 - Add -pthread to gmodule pkg-config
gobject-2.0-uninstalled.pc.in Enable threads in g_type_init()
gobject-2.0.pc.in Enable threads in g_type_init()
gthread-2.0-uninstalled.pc.in Default to --disable-gtk-doc, to avoid Jade setup hassles.
gthread-2.0.pc.in Default to --disable-gtk-doc, to avoid Jade setup hassles.
makefile.msc added glib_gettext (in use by gio) also try building gio
mkinstalldirs mkinstalldirs: Update to latest version
msvc_recommended_pragmas.h removed -GD to compile with msvc9 (vs2008) with less complains
sanity_check Replace bash-specific == with sh-understood =. Fixes bug #373864.
win32-fixup.pl adapt to recent api changes variable declaration at the beginning of a

README.commits

GLib is part of the GNOME git repository. At the current time, any
person with write access to the GNOME repository, can make changes to
GLib. This is a good thing, in that it encourages many people to work
on GLib, and progress can be made quickly. However, GLib is a fairly
large and complicated package that many other things depend on, so to
avoid unnecessary breakage, and to take advantage of the knowledge
about GLib that has been built up over the years, we'd like to ask
people committing to GLib to follow a few rules:

0) Ask first. If your changes are major, or could possibly break existing
   code, you should always ask. If your change is minor and you've
   been working on GLib for a while it probably isn't necessary
   to ask. But when in doubt, ask. Even if your change is correct,
   somebody may know a better way to do things.

   If you are making changes to GLib, you should be subscribed
   to gtk-devel-list@gnome.org. (Subscription address:
   gtk-devel-list-request@gnome.org.) This is a good place to ask
   about intended changes.

   #gtk+ on GIMPNet (irc.gimp.org, irc.us.gimp.org, irc.eu.gimp.org, ...)
   is also a good place to find GTK+ developers to discuss changes with,
   however, email to gtk-devel-list is the most certain and preferred
   method.

1) Ask _first_.

2) With git, we no longer maintain a ChangeLog file, but you are expected
   to produce a meaningful commit message. Changes without a sufficient
   commit message will be reverted. See below for the expected format
   of commit messages.

Notes:

* When developing larger features or complicated bug fixes, it is
  advisable to work in a branch in your own cloned GLib repository.
  You may even consider making your repository publically available
  so that others can easily test and review your changes.

* The expected format for git commit messages is as follows:

=== begin example commit ===
Short explanation of the commit

Longer explanation explaining exactly what's changed, whether any
external or private interfaces changed, what bugs were fixed (with bug
tracker reference if applicable) and so forth. Be concise but not too brief.
=== end example commit ===

  - Always add a brief description of the commit to the _first_ line of
    the commit and terminate by two newlines (it will work without the
    second newline, but that is not nice for the interfaces).

  - First line (the brief description) must only be one sentence and
    should start with a capital letter unless it starts with a lowercase
    symbol or identifier. Don't use a trailing period either. Don't exceed
    72 characters.

  - The main description (the body) is normal prose and should use normal
    punctuation and capital letters where appropriate. Normally, for patches
    sent to a mailing list it's copied from there.

  - When committing code on behalf of others use the --author option, e.g.
    git commit -a --author "Joe Coder <joe@coder.org>" and --signoff.


Owen Taylor
13 Aug 1998
17 Apr 2001

Matthias Clasen
31 Mar 2009
Something went wrong with that request. Please try again.