commit 5cd352c13272e2d518d624037052c87a12f65d7e
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Sun Jun 9 18:53:15 2013 -0400

    2.36.3

 NEWS | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

commit cbb8446c1dbffb390b20c5425c7b975be4bfb8fa
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Thu Jun 6 00:05:41 2013 -0400

    Update link to documentation

 gio/gapplicationimpl-dbus.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit f269f51ed3f8253ec6b96e5a26032dfc84a7e2ce
Author: Colin Walters <walters@verbum.org>
Date:   Wed Jun 5 18:05:12 2013 -0400

    GFileEnumerator: Add some documentation about ordering

    Kind of a gratuitious gaping hole in the docs...

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

 gio/gfileenumerator.c | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

commit c2ad7d1aa549deff6e0ab34e6981a8f794df729c
Author: Dan Winship <danw@gnome.org>
Date:   Sun Jun 2 18:32:21 2013 -0300

    ginetaddress: fix addr/string conversions on windows

    When parsing an address, we need to re-set "len" between IPv4 and
    IPv6, since WSAStringToAddress() might set it to sizeof(struct
    sin_addr)
    when trying to parse the string as IPv4, even if it fails. Also, we
    need to make sure to not pass strings to WSAStringToAddress() that it
    will accept but that we don't want it to.

    When stringifying an address, we need to clear the sockaddr before
    filling it in, so we don't accidentally end up with an unwanted
    scope_id or the like.

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

 gio/ginetaddress.c | 29 +++++++++++++++++++++--------
 1 file changed, 21 insertions(+), 8 deletions(-)

commit ffddb55ab3ef781822adfad1f64b32a2f1ef09a9
Author: Colin Walters <walters@verbum.org>
Date:   Sun May 12 07:28:01 2013 +0100

    Ensure g_file_copy() does not temporarily expose private files

    Previously, g_file_copy() would (on Unix) create files with the
    default mode of 644.  For applications which might at user request
    copy arbitrary private files such as ~/.ssh or /etc/shadow, a
    world-readable copy would be temporarily exposed.

    This patch is suboptimal in that it *only* fixes g_file_copy()
    for the case where both source and destination are instances of
    GLocalFile on Unix.

    The reason for this is that the public GFile APIs for creating files
    allow very limited control over the access permissions for the created
    file; one can either say a file is "private" or not.  Fixing
    this by adding e.g. g_file_create_with_attributes() would make sense,
    except this would entail 8 new API calls for all the variants of
    _create(), _create_async(), _replace(), _replace_async(),
    _create_readwrite(), _create_readwrite_async(), _replace_readwrite(),
    _replace_readwrite_async().  That can be done as a separate patch
    later.

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

 gio/gfile.c                  | 24 +++++++++++++++++++++++-
 gio/glocalfile.c             | 23 ++++++++++++++---------
 gio/glocalfile.h             |  2 ++
 gio/glocalfileoutputstream.c | 36 ++++++++++++++++++++++--------------
 gio/glocalfileoutputstream.h |  2 ++
 5 files changed, 63 insertions(+), 24 deletions(-)

commit ae82af8da06f57f10ae9a0b74e89a02fa9c8babf
Author: Colin Walters <walters@verbum.org>
Date:   Thu May 9 00:01:59 2013 +0100

    g_file_copy(): Clean up logic for info query

    Previously, we called g_file_query_info() *again* on the source at the
    very end of the copy.  This has the lame semantics that if the source
    happened to be deleted, we would fail to apply attributes to the
    destination.  This could even be a security flaw.

    This commit changes things so that we query info from the source
    *stream* after opening - i.e. on Unix we use the proper fstat() and
    friends.  That way we operate more atomically.

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

 gio/gfile.c | 128
 +++++++++++++++++++++++++++++++++++++++++-------------------
 1 file changed, 88 insertions(+), 40 deletions(-)

commit cf1922965a897cbfb53ac3e88c2a444f880b01d7
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Tue Jun 4 09:48:12 2013 -0400

    g_file_set_contents(): don't fsync on ext3/4

    ext3 and ext4 (for quite some time) with default mount options don't
    need fsync() to ensure safety of replace-by-rename.  Stop doing
    that for
    these filesystems.

    Note: this patch also impacts ext2, which is probably not safe, but I
    don't know of any way to check ext2. vs the others because they
    all have
    the same magic numbers (short of opening /proc/mount).

    This patch assumes that if BTRFS_SUPER_MAGIC is defined then so
    will be
    EXT3_SUPER_MAGIC.

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

 glib/gfileutils.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

commit ee8d3333ddc350da5853707c31169af866fc4524
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Mon Jun 3 22:55:20 2013 -0400

    g_file_set_contents: change {posix_ => }fallocate

    Use fallocate() instead of posix_fallocate() so that we just fail
    instead of getting the emulated version from the libc.

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

 configure.ac      | 2 +-
 glib/gfileutils.c | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

commit c244222d65d2e9c1fe05e46207a7aedde45e1e86
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Mon Jun 3 17:59:29 2013 -0400

    g_file_set_contents(): fix simple logic error

    CI FTW.

 glib/gfileutils.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit dad3cb55cf357b3bae7f02bdc8fc4a8473db0388
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Mon Jun 3 17:49:06 2013 -0400

    g_file_set_contents(): use unistd instead of stdio

    Use a normal write() system call instead of fdopen() and fwrite().

    This will definitely work on UNIX system and should work on Windows as
    well...

    As an added bonus, we can use g_close() now as well.

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

 glib/gfileutils.c | 52
 +++++++++++++++++++---------------------------------
 1 file changed, 19 insertions(+), 33 deletions(-)

commit 75c0593a268b5ceb0cc7ac84d52e23a93a3f2e9d
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Mon Jun 3 16:16:25 2013 -0400

    g_file_set_contents(): don't allocate display name

    g_file_set_contents() sets a GError in the event of various failures
    that count occur.  It uses g_filename_display_name() in order to
    get the
    filename to include in the messages.

    Factor out the error handling to make it easier to allocate the
    display
    name only when we need it (instead of allocating it every time).

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

 glib/gfileutils.c | 124
 ++++++++++++++++++++----------------------------------
 1 file changed, 46 insertions(+), 78 deletions(-)

commit 2d827a25af4bea0513d5fc0796b139337278734b
Author: Ryan Lortie <desrt@desrt.ca>
Date:   Mon Jun 3 15:43:01 2013 -0400

    g_file_set_contents(): use posix_fallocate()

    Extents-based filesystems like knowing in advance how much data
    will be
    written to a file in order to prevent fragmentation.  If we have
    it, use
    posix_fallocate() before writing data in g_file_set_contents().

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

 configure.ac      | 2 +-
 glib/gfileutils.c | 7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)

commit 5d1969c8cb7e4f380f4de3c848425f3aba4b7445
Author: William Jon McCann <jmccann@redhat.com>
Date:   Wed Jan 30 00:46:43 2013 +0100

    Fix property example in gobject tutorial

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

 docs/reference/gobject/tut_howto.xml | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

commit a2f1b4b60e2cc5934df3b1c5b1de9415e229cee2
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Tue May 28 22:23:58 2013 -0400

    Trivial doc typo fix

 gobject/gtype.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

commit 6e4b7a4ab8e5b1fe62e28f368fa305864f79c315
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Wed May 29 00:07:26 2013 -0400

    Trivial documentation typos

 gobject/gobject.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

commit baed05fbeaa30d4e3b82581388a22cc75bf9a311
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Sat May 25 23:07:03 2013 -0400

    Avoid a segfault in gdbus tool

    When the interface name is invalid, we don't get an error
    back from g_dbus_connection_call_sync.

 gio/gdbus-tool.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

commit b14e899b5e03cf8120309081f0afbb898ed59235
Author: Simon Kågedal Reimer <skagedal@gmail.com>
Date:   Mon May 6 22:04:32 2013 +0200

    G_GNUC_FORMAT: documentation error

    Attribute should be placed just before the semicolon, not after.
    As can be seen in the example.

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

 glib/docs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit bc9470f3c8b3984f68c74b30aae5f5b11e50f2cd
Author: Jason L. Quinn <jason.lee.quinn@gmail.com>
Date:   Thu Apr 11 23:43:17 2013 -0400

    spelling fixes of 'runtine' and 'adresses' in cross.xml and
    running.xml, respectively

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

 docs/reference/glib/cross.xml   | 2 +-
 docs/reference/glib/running.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

commit 03d3a53876b8e015a8f4f428fe31b15b5d8ec300
Author: Giovanni Campagna <gcampagna@src.gnome.org>
Date:   Fri Mar 29 15:39:26 2013 +0100

    GThreadedResolver: set an error if no records could be found

    It is possible that the upstream servers return something, but
    we then filter all results because they are of the wrong type.
    In that case the API and subsequent GTask calls expect a GError
    to be set.

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

 gio/gthreadedresolver.c | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

commit 36284c5d59ccbe2a62fd506307d92991291038aa
Author: Chun-wei Fan <fanchunwei@src.gnome.org>
Date:   Mon May 27 15:57:54 2013 +0800

    Fix the GObject Visual Studio Projects

    Update G_LOG_DOMAIN to be "GLib-GObject" so that we are consistent
    with
    the autotools builds, and that tests expecting the log domain to be
    "GLib-GObject" would not fail.

 build/win32/vs10/gobject.vcxprojin | 8 ++++----
 build/win32/vs9/gobject.vcprojin   | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

commit f3b1bab8ada59b6e52eeb74a8872eeb82777baba
Author: Chun-wei Fan <fanchunwei@src.gnome.org>
Date:   Mon May 27 13:23:58 2013 +0800

    Fix the GLib Visual Studio Projects

    Define the G_LOG_DOMAIN of the GLib DLL as "GLib", because:
    -This makes it consistent with the autotools builds
    -Some tests expect the log domain to be "GLib"

 build/win32/vs10/glib.vcxprojin | 16 ++++++++--------
 build/win32/vs9/glib.vcprojin   | 16 ++++++++--------
 2 files changed, 16 insertions(+), 16 deletions(-)

commit e7ba0c489a6a660ca209dde089a0d712e03eb803
Author: Shankar Prasad <svenkate@redhat.com>
Date:   Tue May 14 15:27:33 2013 +0530

    updated kn translations

 po/kn.po | 395
 +++++++++++++++++++++++++++++++--------------------------------
 1 file changed, 192 insertions(+), 203 deletions(-)

commit ced0cea5bbd468713d216db4c4da2abc28957123
Author: Matthias Clasen <mclasen@redhat.com>
Date:   Mon May 13 09:59:47 2013 -0400

    Bump versin

 configure.ac | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)