Commits on Sep 17, 2010
  1. release 2.25.16

    desrt committed Sep 17, 2010
  2. GDateTime: fix a test that fails from time to time

    The test fails if it's a different date in the time zone of the machine
    running the test than it currently is in UTC.
    desrt committed Sep 17, 2010
  3. .gitignore some test cases

    desrt committed Sep 17, 2010
  4. .gitignore some sgml

    desrt committed Sep 17, 2010
  5. Deal with gtk-doc's insane sensitivty to spaces inserting a few of them.
    desrt committed Sep 17, 2010
  6. datetime: Fix hashing

    Convert to the epoch, just like we do when checking for equality, so
    that timezones are correctly handled.
    Emmanuele Bassi committed with desrt Sep 15, 2010
  7. datetime: Rename g_date_time_printf() to g_date_time_format()

    The function does not use any printf() modifiers, so using printf() is a
    Prior art: strftime, g_ascii_formatd
    Emmanuele Bassi committed with desrt Sep 15, 2010
  8. datetime: Update modifiers for DST changes

    If a DateTime gets modified to cross the DST state from its previous
    state then we want to update the DateTime to compensate for the new
    In other words, if we have a DateTime defined as:
      DateTime({ y: 2009, m: 8, d: 15, hh: 3, mm: 0, tz: 'Europe/London' });
    and we add six months to it, the hour must be changed to 60 minutes
    behind, as the DST comes into effect.
    Emmanuele Bassi committed with desrt Sep 15, 2010
  9. datetime: Allow setting fractionary seconds in new_full()

    Otherwise we'll have to do:
      dt = g_date_time_new_full (Y, M, D, h, m, s, tz);
      tmp = g_date_time_add_usec (dt, usec);
      g_date_time_unref (dt);
      dt = tmp;
    With its additional allocations.
    Emmanuele Bassi committed with desrt Sep 15, 2010
  10. datetime: Rework time zone support in constructors

    Timezone handling is complicated. Really complicated.
    In order to simplify it a little bit, we need to expose the GTimeZone
    First of all, we allow creating time zone information directly from the
    offset and the DST state, and then pass it to the g_date_time_new_full()
    constructor. We also need to clean up the mess that is UTC-vs.-localtime
    for the other constructors.
    We also allow creating a GTimeZone from the Olson zoneinfo database
    names; a time zone created like this will be "floating": it will just
    reference the zoneinfo file - which are mmap()'ed, kept in a cache and
    refcounted. Once the GTimeZone has been associated with a GDateTime, it
    will be "anchored" to it: the offset will be resolved, as well as the
    DST state.
    Emmanuele Bassi committed with desrt Sep 14, 2010
  11. Updated Lithuanian translation

    Žygimantas Beručka committed Sep 17, 2010
Commits on Sep 16, 2010
Commits on Sep 15, 2010
  1. Update Czech translation

    pmkovar committed Sep 15, 2010
  2. Update Czech translation

    pmkovar committed Sep 15, 2010
  3. Bug 629709 - Empty variants

    Fix some GVariant bugs uncovered by calling g_variant_new_from_data with
    invalid data (which it should be immune to).
    desrt committed Sep 15, 2010
  4. Updated Spanish translation

    Jorge González committed Sep 15, 2010
Commits on Sep 14, 2010
  1. GDBusConnection leaks its GCredentials

    ==7269== 144 bytes in 6 blocks are definitely lost in loss record 1,282 of 1,325
    ==7269==    at 0x4005BDC: malloc (vg_replace_malloc.c:195)
    ==7269==    by 0x4056B74: g_malloc (gmem.c:164)
    ==7269==    by 0x406EDB6: g_slice_alloc (gslice.c:842)
    ==7269==    by 0x406EDFB: g_slice_alloc0 (gslice.c:854)
    ==7269==    by 0x413C627: g_type_create_instance (gtype.c:1867)
    ==7269==    by 0x412276A: g_object_constructor (gobject.c:1480)
    ==7269==    by 0x4121E5D: g_object_newv (gobject.c:1264)
    ==7269==    by 0x4121BD3: g_object_new (gobject.c:1176)
    ==7269==    by 0x417CFB9: g_credentials_new (gcredentials.c:156)
    ==7269==    by 0x41D9DBC: g_unix_credentials_message_deserialize (gunixcredentialsmessage.c:149)
    ==7269==    by 0x41C422C: g_socket_control_message_deserialize (gsocketcontrolmessage.c:198)
    ==7269==    by 0x41BFCE3: g_socket_receive_message (gsocket.c:3289)
    ==7269==    by 0x41D99CE: g_unix_connection_receive_credentials (gunixconnection.c:476)
    ==7269==    by 0x41FA829: _g_dbus_auth_run_server (gdbusauth.c:987)
    ==7269==    by 0x4205DDB: initable_init (gdbusconnection.c:2196)
    Bug #629689.
    Christian Persch committed Sep 14, 2010
  2. GVariant: Check for size == 0 in get_bytestring

    And add a test from David that shows the problem.
    Closes #629698
    desrt committed Sep 14, 2010
  3. Updated Polish translation

    piotrdrag committed with TomaszDom Sep 14, 2010
  4. GSettings: reverse accidental addition to .h file

    A couple of extra function prototypes snuck into commit
    77e3bad.  Take those out.
    desrt committed Sep 14, 2010
  5. Updated Hungarian translation

    kelemeng committed Sep 14, 2010
  6. [l10n] Updated German translation

    Christian.Kirbach committed Sep 14, 2010
Commits on Sep 13, 2010
  1. Updated Slovenian translation

    urmatej committed Sep 13, 2010
  2. g_strdup_value_contents(): dump GStrv more usefully

    Previously, dumping a GValue holding a GStrv just yielded "((GStrv *)
    0xDEADBEEF)". I think it'd be more useful to dump a Python list-style
    representation of the GStrv's contents, if it's not NULL.
    Fixes: <>
    Will Thompson committed Sep 9, 2010
  3. update for Punjabi

    A S Alam committed Sep 13, 2010
  4. Add g_data_input_stream_read_upto{,async,finish}

    These functions are meant to replace the read_until() flavour, with the
    following improvements:
      - consistency between the synchronous and asynchronous versions as to
        if the separator character is read (it never is).
      - support for using a nul byte as a separator character by way of
        addition of a length parameter which allows stop_chars to be treated
        as a byte array rather than a nul-terminated string.
    The read_until() functions are not yet formally deprecated, but a note
    has been added to the documentation warning not to use them as they will
    be in the future.
    This is bug #584284.
    desrt committed Mar 23, 2010
  5. Better msgctxt for month and weekday names

    The current msgctxt string 'GDateTime" lead to the unability to
    differentiate between the full and abbreviated name for May.
    Therefore, the msgctxt strings have been changed to
      'full month name'
      'abbreviated month name'
      'full weekday name'
      'abbreviated weekday name'
    This is a string change, but all translations have been updated
    using an sed script.
    Bug 629429
    Matthias Clasen committed Sep 13, 2010