Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Warning: the windows branch is treated as a local topic branch that just happens to be shared here, so expect non-fast-forward updates...
C Objective-C Python C++ Perl Shell

[WIP] Fix Python shebang lines.

This avoids using a hard-coded value for the shebang, as
previously discussed in bug #650763.
latest commit 80ad766190
@dieterv authored
Failed to load latest commit information.
build Visual C++ 2010 projects: Prepare support for VS2012
docs Add an option to make glib-compile-resources use G_GNUC_INTERNAL
gio [WIP] Fix Python shebang lines.
glib [WIP] Fix Python shebang lines.
gmodule win32: remove old "locale encoded filename parameter" dll abi compati…
gobject win32: remove old "locale encoded filename parameter" dll abi compati…
gthread win32: define STRICT by default when building glib
m4macros configure: Enable set of standard -Werror=foo flags
po Updated Serbian translation
tests tests: fix printf precision format
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C
.gitignore .gitignore: ignore .def files (win32 build)
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 Some minor updates of HACKING 2.34.0 win32: define STRICT by default when building glib
Makefile.decl Pass G_DEBUG=g-gc-friendly when running the tests
NEWS Release GLib 2.35.1
NEWS.pre-1-3 updates.
README.commits Update README files to refer to git Note undefined behavior with new g_type_init() -> ctor change
README.win32 Update Win32 and VS Readme files
acglib.m4 Update GLIB_CHECK_COMPILE_WARNINGS macro to work with Autoconf 2.64
acinclude.m4 Move some inter-*.m4 includes from to acinclude.m4 to avoid Fix problems with CLEANFILES and automake-1.11.1 Update config.h.win32(.in) and glibconfig.h.win32(.in) properly quote AC_MSG_CHECKING gio-2.0.pc: Avoid full path to executables gio: Move gmodule to Requires.private Add GWin32InputStream and GWin32OutputStream classes Beef up Libs.private in glib-2.0.pc Fix path to aclocal in output message Add gdbus-codegen to
glib.doap update maintainers in glib.doap Bug 600141 - Add -pthread to gmodule pkg-config Bug 600141 - Add -pthread to gmodule pkg-config Bug 600141 - Add -pthread to gmodule pkg-config gobject.pc: remove dependency on gthread Default to --disable-gtk-doc, to avoid Jade setup hassles.
makefile.msc added glib_gettext (in use by gio) also try building gio
msvc_recommended_pragmas.h msvc_recommended_pragmas.h: Re-enable C4819 warnings
sanity_check Replace bash-specific == with sh-understood =. Fixes bug #373864. adapt to recent api changes variable declaration at the beginning of a


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 (Subscription address: This is a good place to ask
   about intended changes.

   #gtk+ on GIMPNet (,,, ...)
   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

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.


* 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 <>" and --signoff.

Owen Taylor
13 Aug 1998
17 Apr 2001

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