1. 26 Jun, 2018 1 commit
  2. 14 Jun, 2018 1 commit
  3. 04 Jun, 2018 1 commit
  4. 29 Nov, 2017 1 commit
  5. 12 Nov, 2017 1 commit
  6. 07 Nov, 2017 1 commit
    • Cosimo Cecchi's avatar
      gmain: add g_clear_handle_id API · 5ebd8f6e
      Cosimo Cecchi authored
      It's a very common pattern to see code that looks like this in
      dispose() or finalize() implementations:
      
      if (priv->source_id > 0)
        {
          g_source_remove (priv->source_id);
          priv->source_id = 0;
        }
      
      This API allows to accomplish the same goal with a single line:
      
      g_clear_handle_id (&priv->source_id, (GClearHandleFunc) g_source_remove);
      
      Thanks to Emmanuele Bassi <ebassi@gnome.org> for making the patch
      generic.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=788489
      5ebd8f6e
  7. 24 May, 2017 1 commit
    • Sébastien Wilmet's avatar
      glib/: LGPLv2+ -> LGPLv2.1+ · f9faac76
      Sébastien Wilmet authored
      All glib/*.{c,h} files have been processed, as well as gtester-report.
      
      12 of those files are not licensed under LGPL:
      
      	gbsearcharray.h
      	gconstructor.h
      	glibintl.h
      	gmirroringtable.h
      	gscripttable.h
      	gtranslit-data.h
      	gunibreak.h
      	gunichartables.h
      	gunicomp.h
      	gunidecomp.h
      	valgrind.h
      	win_iconv.c
      
      Some of them are generated files, some are licensed under a BSD-style
      license and win_iconv.c is in the public domain.
      
      Sub-directories inside glib/:
      
      	deprecated/: processed in a previous commit
      	glib-mirroring-tab/: already LGPLv2.1+
      	gnulib/: not modified, the code is copied from gnulib
      	libcharset/: a copy
      	pcre/: a copy
      	tests/: processed in a previous commit
      
      https://bugzilla.gnome.org/show_bug.cgi?id=776504
      f9faac76
  8. 25 Apr, 2017 1 commit
    • Philip Withnall's avatar
      gmain: Allow GSource methods to be called from a finalize() callback · 281e3010
      Philip Withnall authored
      Temporarily increase the ref count of a GSource to 1 while calling its
      finalize() callback, so that the finalize() implementation can call
      GSource methods (like g_source_set_ready_time()) without causing
      critical warnings. It’s safe to call those methods at this point, as the
      source has been destroyed, but nothing has been freed.
      
      This is an indirect way of fixing a race between GCancellable and
      GCancellableSource, whereby the GCancellable::cancelled callback for the
      GCancellableSource is not disconnected until the GCancellableSource’s
      finalize() function is called. Previously, this meant there was a window
      in which the GCancellableSource’s ref count was 0, but the ::cancelled
      callback was still connected, and could legitimately be called as a
      result of another thread calling g_cancellable_cancel() on the
      GCancellable. The callback calls g_source_set_ready_time() on the
      GSource, and there’s no thread-safe way of checking whether the GSource
      has been destroyed. Instead, we have to change GSource so its ref count
      is only decremented to 0 inside the locked section in
      g_source_unref_internal() *after* the finalize() function has been
      called, and hence after the GCancellable::cancelled callback has been
      disconnected. The use of g_cancellable_disconnect() ensures that the
      callback disconnection is thread safe.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
      
      https://bugzilla.gnome.org/show_bug.cgi?id=781601
      281e3010
  9. 09 Nov, 2016 1 commit
  10. 29 Jun, 2016 1 commit
  11. 02 Aug, 2015 1 commit
  12. 31 May, 2014 1 commit
  13. 31 Jan, 2014 1 commit
  14. 20 Sep, 2013 1 commit
  15. 20 Jul, 2013 1 commit
  16. 13 Jul, 2013 1 commit
  17. 15 Jan, 2013 5 commits
  18. 13 Jan, 2013 1 commit
  19. 28 Dec, 2012 1 commit
  20. 10 Jul, 2012 1 commit
    • Colin Walters's avatar
      Add g_spawn_check_exit_status() · f7abd3ce
      Colin Walters authored
      Many (if not "almost all") programs that spawn other programs via
      g_spawn_sync() or the like simply want to check whether or not the
      child exited successfully, but doing so requires use of
      platform-specific functionality and there's actually a fair amount of
      boilerplate involved.
      
      This new API will help drain a *lot* of mostly duplicated code in
      GNOME, from gnome-session to gdm.  And we can see that some bits even
      inside GLib were doing it wrong; for example checking the exit status
      on Unix, but ignoring it on Windows.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=679691
      f7abd3ce
  21. 02 Jul, 2012 1 commit
  22. 27 Feb, 2012 1 commit
  23. 27 Dec, 2011 1 commit
  24. 14 Dec, 2011 1 commit
  25. 03 Nov, 2011 2 commits
  26. 12 Oct, 2011 1 commit
  27. 11 Oct, 2011 1 commit
  28. 09 Oct, 2011 1 commit
  29. 07 Oct, 2011 1 commit
  30. 10 Sep, 2011 1 commit
  31. 31 Aug, 2011 2 commits
  32. 29 Aug, 2011 1 commit
    • Colin Walters's avatar
      gdatetime: Add g_date_time_source_new() · 1feb7529
      Colin Walters authored
      Several different codebases in GNOME want to implement wall clocks.
      While we could pretty easily share a private library, it's not a
      substantial amount of code, and GLib already has a lot of the
      necessary system-specific detection and handling infrastructure.
      
      Note this initial implementation just wakes up once a second in the
      cancel_on_set case; we'll add the Linux-specific handling in a
      subsequent commit.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=655129
      1feb7529
  33. 09 Jun, 2011 2 commits