1. 13 Oct, 2016 1 commit
  2. 10 Oct, 2016 1 commit
  3. 19 Sep, 2016 1 commit
  4. 18 Sep, 2016 1 commit
  5. 13 Sep, 2016 1 commit
  6. 28 Aug, 2016 1 commit
  7. 17 Aug, 2016 1 commit
  8. 28 Jul, 2016 1 commit
  9. 26 Jul, 2016 1 commit
  10. 23 Jul, 2016 1 commit
    • Matthias Clasen's avatar
      Drop libsystemd dependency · 6a07885a
      Matthias Clasen authored
      Talk to the journal ourselves using sendmsg() instead of linking
      against libsystemd for sd_journal_sendv(). At the same time, we
      can also avoid excessive copying.
      
      The motivation for dropping the dependency is that we can
      then use structured logging e.g. in a flatpak sandbox where
      libsystemd may not be present in the runtime.
      
      The code here is inspired by similar code in libvirt.
      6a07885a
  11. 21 Jul, 2016 1 commit
  12. 17 Jul, 2016 1 commit
    • Philip Withnall's avatar
      gmessages: Add a structured logging API · 052eaf24
      Philip Withnall authored
      In parallel with g_log(), add a new structured logging API, based around
      g_log_structured() and various helper functions which are exposed
      publicly to allow programs to build their own logging policies easily,
      without having to rewrite a lot of gmessages.c because it’s all
      internal.
      
      See the expanded documentation at the top of gmessages.c for some
      rationale. See the g_log_structured() documentation for some example
      code.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=744456
      052eaf24
  13. 29 Jun, 2016 1 commit
  14. 28 Jun, 2016 1 commit
    • Ondrej Holy's avatar
      fileinfo: Add G_FILE_ATTRIBUTE_FILESYSTEM_REMOTE attribute · e57355b0
      Ondrej Holy authored
      Add filesystem attribute to detect remote filesystems in order to
      replace hardcoded filesystem types in GtkFileSystem. Set this attribute
      also for GLocalFile appropriately.
      
      Bump version to 2.49.3, so that early adopters of new API have a version
      number to target.
      e57355b0
  15. 20 Jun, 2016 1 commit
  16. 20 May, 2016 1 commit
  17. 27 Apr, 2016 1 commit
  18. 26 Apr, 2016 2 commits
  19. 04 Apr, 2016 1 commit
  20. 22 Mar, 2016 1 commit
  21. 16 Mar, 2016 1 commit
  22. 25 Feb, 2016 1 commit
    • Chun-wei Fan's avatar
      Visual Studio builds: Move @GLIB_VERSION@ usage · 99b30f38
      Chun-wei Fan authored
      ... from glib-gen-srcs.[vsprops|props].in to
      glib-version-paths.[vsprops|props].in, and instead let autotools generate
      glib-version-paths.[vsprops|props] rather than
      glib-gen-srcs.[vsprops|props], as this will need to be referenced for
      other items as well, namely generating the .pc files which will become
      useful for introspection builds.
      99b30f38
  23. 16 Feb, 2016 1 commit
  24. 24 Jan, 2016 1 commit
  25. 18 Jan, 2016 1 commit
  26. 14 Jan, 2016 1 commit
  27. 10 Jan, 2016 1 commit
  28. 09 Jan, 2016 1 commit
  29. 16 Dec, 2015 2 commits
  30. 08 Dec, 2015 1 commit
  31. 25 Nov, 2015 1 commit
  32. 24 Nov, 2015 2 commits
  33. 16 Nov, 2015 1 commit
    • Allison Karlitskaya's avatar
      GLib: clean up the "inline" mess once and for all · db2367e8
      Allison Karlitskaya authored
      It's been a long time since we've been unconditionally saying "static
      inline" in GLib headers without complaints so it's safe to assume that
      all compilers that we care about support this.
      
      One thing that is not yet totally supported is the unadorned use of the
      word "inline".  Depending on the flags (-std=c89, for example), even GCC
      will complain about this.  Detect missing C99 support and define
      "inline" to "__inline" in that case.  Some research shows "__inline"
      appears to be the most widely-supported keyword here, but we may need to
      tweak this if we get some reports of breakage.
      
      Clean up all of the configure checks around this and define G_CAN_INLINE
      unconditionally.  Unfortunately, we must assume that some people are
      still using G_IMPLEMENT_INLINES, we must continue to implement that
      (including undefining G_CAN_INLINE and redefining G_INLINE_FUNC) if
      requested.
      
      It is not our intent to break existing users of the old-style
      G_INLINE_FUNC approach and if that has happened, we may need to make
      some further adjustments.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=757374
      db2367e8
  34. 02 Nov, 2015 1 commit
  35. 26 Oct, 2015 1 commit
  36. 20 Oct, 2015 1 commit
  37. 01 Oct, 2015 1 commit