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

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