Fix a typo
Simplify coverage rules

This works just fine, no need for the manual removal of the
info file.
More test coverage for settings backends
GKeyfileSettingsBackend: Use a directory monitor

GKeyfileSettingsBackend was using a file monitor to monitor
the parent directory of its keyfile.
More settings backend tests

This adds some more test coverage around writability changes
in the keyfile and delayed settings backends.
GVariant: Add g_variant_parse_error_quark()

Most GErrors, such as GSomethingError, have a function to get
their quark that looks like g_something_error_quark(),
so bindings (such as gtkmm) would expect GVariantParseError
to have g_variant_parse_error_quark(). Instead this had
g_variant_parser_get_error_quark().
This deprecates the old function and adds the correct one,
making life easier for gtkmm (and maybe others).

https://bugzilla.gnome.org/show_bug.cgi?id=708212
Use POSIX-specified <poll.h> over <sys/poll.h>

POSIX specifies that <poll.h> is the correct header to include for
poll(), so let's do that instead.

https://bugzilla.gnome.org/show_bug.cgi?id=141251
GVariant: add way to print context of parse errors

This was a feature intended from the very beginning that somehow never
got written.  It's a way to replace these sort of error messages out of
the GVariant parser:

  1-2,10-15:unable to find a common type

with something in the style of the Vala compiler:

  unable to find a common type:
    [1, 2, 3, 'str']
     ^        ^^^^^

https://bugzilla.gnome.org/show_bug.cgi?id=715028
gsettings tool: print GVariant errors in context

Use g_variant_parse_error_print_context() to format the error message
from the GVariant parser.

https://bugzilla.gnome.org/show_bug.cgi?id=715028
gapplication(1): print GVariant errors in context

Use g_variant_parse_error_print_context() to format the error message
from the GVariant parser.

https://bugzilla.gnome.org/show_bug.cgi?id=715028
gdbus tool: print GVariant errors in context

Use g_variant_parse_error_print_context() to format the error message
from the GVariant parser.

There is a slightly dubious interaction with the "parse me harder"
functionality here.  We're probably going to have to deal with that
separately.

https://bugzilla.gnome.org/show_bug.cgi?id=715028
Revert "gsettings m4: check for .xml in src/builddir"

This reverts commit b3593693d918f0ae97094f6712d817180b8eea6a.

See: https://bugzilla.gnome.org/show_bug.cgi?id=712171#c3
See: https://bugzilla.gnome.org/show_bug.cgi?id=712171#c4

Tested using both srcdir == builddir and srcdir != builddir in hotssh.

Conflicts:
	m4macros/gsettings.m4

https://bugzilla.gnome.org/show_bug.cgi?id=712630
gio: Fix return of value from void function

https://bugzilla.gnome.org/show_bug.cgi?id=721034
gdbus: Prevent polling on a closed DBus connection
Pluggable backends for GMainContext

The backends can be applied dynamically along with acquire/release semantics
with the new methods, g_main_context_enter_poller and
g_main_context_leave_poller.
A simple test for polling on a file-like descriptor
glib/tests/mainloop: Acquire the context while asserting its state

The iteration methods presume that the context is acquired.