Add a new GLIB_CONFIG macro, which is mostly similar to the old
AM_PATH_GLIB_2_0, but correctly namespaced, and with parts of
GLIB_GSETTINGS added, and support for GLIB_VERSION_MIN_REQUIRED and
GLIB_VERSION_MAX_ALLOWED.

Add a new glib-build.mk with rules to generate enumtypes files,
marshallers, gsettings schemas, and resource files, so that people
don't have to copy and paste the rules into every project's
Makefile.am

https://bugzilla.gnome.org/show_bug.cgi?id=654395

Allow only format strings that copy all values (i.e, don't contain '&'),
as the returned pointers might become invalid in some rare cases.

Since this is technically an API break, this patch only prints a
critical when a faulty format string is detected, but still fetches the
values.

https://bugzilla.gnome.org/show_bug.cgi?id=719979

https://bugzilla.gnome.org/show_bug.cgi?id=712148

https://bugzilla.gnome.org/show_bug.cgi?id=719884

Note this explicitly so that people can rely on doing:

if (mystruct->sigid > 0)
  g_signal_disconnect (mystruct->object, mystruct->sigid);

https://bugzilla.gnome.org/show_bug.cgi?id=719809

As recommended by Christian Persch.

https://bugzilla.gnome.org/show_bug.cgi?id=711546

Commit e53caad4 makes _g_log_abort() noreturn by calling abort()
unconditionally.

However, it is useful to be able to skip some log_abort() with a
debugger, to reach a point of interest. Revert back to previous
behaviour. Make g_assert_warning() noreturn by calling abort().

https://bugzilla.gnome.org/show_bug.cgi?id=711800

This is another crude conditional breakpoint mechanism and can
be done better with actual conditional breakpoints or with systemtap
tracepoints.

https://bugzilla.gnome.org/show_bug.cgi?id=719687

This is really just a very crude and limited conditional breakpoint.
Update the documentation to explain conditional breakpoints in
gdb instead. Also, remove the link to refdbg, which appears dead.

https://bugzilla.gnome.org/show_bug.cgi?id=719687

Usually async methods copy/ref its arguments so caller can
forget about them. g_file_replace_contents_async() and
g_output_stream_write_async() are exceptions.

https://bugzilla.gnome.org/show_bug.cgi?id=690525

https://bugzilla.gnome.org/show_bug.cgi?id=690525

So that it can actually be invoked by bindings.

Be more consistent with the other project file templates, which will
simplify future application of patches.

The desktop-files directory contains a mimeapps.cache file
that was not installed as data for installed tests, causing
the file measure test to fail only in when installed.

Make the testcase compare the byte size to what is reported
by du. Also add a test for the async api, and mak eit test
the progress reporting callback.

https://bugzilla.gnome.org/show_bug.cgi?id=712148

The argv array should be declared as const.

https://bugzilla.gnome.org/show_bug.cgi?id=712148

Shut up, GCC.

https://bugzilla.gnome.org/show_bug.cgi?id=712148

Otherwise, we break in Continuous where /tmp == /sysroot/tmp,
and something in the execve() or the kernel will do realpath()
for us.

Add a test for g_type_class_get_instance_private_offset

Exercise more of the GActionMap implementation.

Add a case that overwrites an existing action.

lcov has the options to generate overview images for each source
file with the --frames option. Lets try this.

This covers some more GSettingsSchemaKey api.

This adds test cases for the Turkish i.

g_settings_get_user_value and g_settings_get_default_value
are now covered.

As per https://bugzilla.gnome.org/show_bug.cgi?id=113075#c39.

Dirk-Jan C. Binnema authored Nov 28, 2013 and Colin Walters committed Nov 28, 2013

Comparing the code generated for the setter and other methods without
(real) return value, I noticed that the setter does not unref the
gvariant it gets.

https://bugzilla.gnome.org/show_bug.cgi?id=719472

The spawnv variant of this function already had a test, but
spawn was not tested.