Skip to content
Commits on Mar 17, 2012
  1. @desrt

    man pages: document the order of schema overrides

    desrt committed
    GSettings overrides are processed in such a way that
    alphabetically-later files have precedence over earlier files (eg: 20_
    will beat 10_).  Document that fact.
  2. @yurayko @ymyasoedov

    Updated Russian translation

    yurayko committed with ymyasoedov
Commits on Mar 16, 2012
  1. @cgwalters

    gmain: Use sig_atomic_t for list of pending Unix signals

    cgwalters committed
    Pointed out by: Simon McVittie <simon.mcvittie@collabora.co.uk>
    
    https://bugzilla.gnome.org/show_bug.cgi?id=671997
  2. @tbzatek

    gio: Only show mounts in /run/media/$USER

    tbzatek committed
    And reflect the recent changes + sync with gvfs+udisks2 rules.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=669797
  3. @davidben @cgwalters

    Continue searching in PATH on ENODEV and ETIMEDOUT

    davidben committed with cgwalters
    Synchronize the error-handling logic from glibc. Users with networked
    filesystems in their PATH may hit ETIMEDOUT.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672201
  4. @cgwalters
  5. @alexlarsson
  6. @alexlarsson

    Make g_array_sort* methods use a stable sort

    alexlarsson committed
    Also, remove previous comments about sort stability in g_array_sort docs,
    as the method that was explained does not work. Adds a new comment
    about this.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672095
  7. @alexlarsson

    Make g_qsort_with_data stable, based on glibc msort

    alexlarsson committed
    We need a stable sort, and we might as well always use it rather
    than have multiple sort versions. This picks up the glibc
    merge sort implementation which it uses by default for qsort,
    except we don't fall back to non-stable quicksort in some cases
    like glibc
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672095
  8. @kelemeng

    Updated Hungarian translation

    kelemeng committed
Commits on Mar 15, 2012
  1. @gforcada

    [l10n]Updated Catalan (Valencian) translation

    Carles Ferrando committed with gforcada
  2. @gforcada
  3. GDBusConnection: Don't store GCancellable in qdata

    David Zeuthen committed
    Now that we're using g_simple_async_result_set_check_cancellable() we
    no longer need this terrible hack of carrying the GCancellable on the
    GSimpleAsyncResult using qdata. See bug 672013 for more details.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672013
    
    Signed-off-by: David Zeuthen <davidz@redhat.com>
  4. @desrt

    GDBus: make use of reliable async cancellation

    desrt committed with David Zeuthen
    Call g_simple_async_result_set_check_cancellable() after all
    GSimpleAsyncResult creation in order to take advantage of the new
    reliable cancellation feature.
    
    The guarantee of reliable cancellation fixes a bug in dbusmenu (which
    was already assuming that cancellation was reliable).  See this bug:
    https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/953562
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672013
    
    Signed-off-by: David Zeuthen <davidz@redhat.com>
  5. @fanc999

    Fix "install" paths in VS property sheets

    fanc999 committed
    ...and cleanup the VS2010 property sheets a little bit
Commits on Mar 14, 2012
  1. @mariobl
  2. @desrt

    GSimpleAsyncResult: support reliable cancellation

    desrt committed
    Add a function g_simple_async_result_set_check_cancellable() to provide
    a GCancellable that is checked for being cancelled during the call to
    g_simple_async_result_propagate_error().
    
    This gives asynchronous operation implementations an easy way to
    provide reliable cancellation of those operations -- even in the case
    that a positive result has occured and is pending dispatch at the time
    the operation is cancelled.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672013
  3. Invalidate single_va_closure when adding an emission hook

    Mike Gorse committed with Matthias Clasen
    If the optimization is used for only having one closure handling a
    signal emission, then hooks will not be run, so it should be disabled
    when an emission hook is added.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=671918
  4. @desrt

    g_log: mask log level before checking prefix flags

    desrt committed
    We check if the log level is in the "prefixed" list by checking it
    against the g_log_msg_prefix bitfield.
    
    Unfortunately we were failing to mask by G_LOG_LEVEL_MASK first, so if
    the FATAL bit was set (for example) then it would never match.  This was
    the case for g_error().
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672026
  5. @desrt

    glib-init: restore default for G_MESSAGES_PREFIXED

    desrt committed
    In the glib-init shuffle this ended up being set to no messages prefixed
    by default.  Fix that so that we have prefixes back.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=672026
  6. @desrt
Commits on Mar 13, 2012
  1. @SuborbitalPigeon
  2. @KennethNielsen
Commits on Mar 12, 2012
  1. @desrt

    GSocketMsgFlags: annotate as a flags

    desrt committed
    This was being incorrectly guessed as an enum.  Fix that.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=671942
  2. Updated Norwegian bokmål translation

    Kjartan Maraas committed
  3. Finnish translation update from http://l10n.laxstrom.name/wiki/Gnome_3.4

    Timo Jyrinki committed
     translation sprint
Commits on Mar 11, 2012
  1. Updated Esperanto translation

    Kristjan SCHMIDT committed
Commits on Mar 9, 2012
  1. @piotrdrag

    Updated Polish translation

    piotrdrag committed
  2. @desrt

    logging test: unset G_MESSAGES_DEBUG

    desrt committed
    Having G_MESSAGES_DEBUG=all in the environment will fail this testcase.
  3. @desrt

    deprecated threads: fix race in GStaticRecMutex

    Mark Janossy committed with desrt
    The very last access to the 'depth' field of GStaticRecMutex in
    g_static_rec_mutex_unlock_full() was being performed after dropping the
    implementation mutex for the last time.
    
    This allowed the lock to be dropped an additional time if it was
    acquired in another thread right at that instant (which is somewhat
    likely, since another thread could have just been woken up by the lock
    being released).
    
    https://bugzilla.gnome.org/show_bug.cgi?id=670846
  4. @alexlarsson

    Fix crash in signal emission optimization

    alexlarsson committed
    The trace of the signal emission of the was calculating the instance
    type after the instance was unrefed. Fix this by keeping the instance type around.
  5. @alexlarsson

    signal emission: Allocate instance_and_param with alloca

    alexlarsson committed
    This Gives a 5% performance increase in e.g. the emit-handled test.
  6. @epienbroek @alexlarsson

    Use native glib-genmarshal when cross-compiling

    epienbroek committed with alexlarsson
    The ability to cross-compile glib got broken after the
    merge of the 'signal-performance' branch as the assumption
    was made that the generated glib-genmarshal can be executed
    on the host (which isn't valid when cross-compiling).
    
    Fixed this by using the just-built glib-genmarshal for normal
    compilations and the native (host) glib-genmarshal when doing a
    cross-compilation as was also done in several other areas of GLib
    
    Tested for host=x86_64-unknown-linux-gnu, target=x86_64-unknown-linux-gnu
    and host=x86_64-unknown-linux-gnu, target=i686-w64-mingw32
    
    https://bugzilla.gnome.org/show_bug.cgi?id=671676
Commits on Mar 8, 2012
  1. @desrt

    gio-querymodules: unlink instead of writing empty cache

    desrt committed
    If there are no modules installed then the most appropriate thing is to
    have no cachefile instead of an empty one.  This unbreaks the "clean
    directory after 'make uninstall'" check that automake does.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=671664
  2. @fanc999

    msvc_recommended_pragmas.h: Silence C4819 warnings

    fanc999 committed
    This warning appears when unicode chars that cannot be displayed in the
    current Windows code page is used anywhere in the file, including comment
    blocks.  We probably don't need to see these, especially as problems
    caused by such characters are manifested as other warnings or errors,
    for example, the need to add BOM to a file when compiling code with
    complex script on Windows.
Something went wrong with that request. Please try again.