1. 15 Mar, 2019 1 commit
  2. 29 May, 2017 1 commit
  3. 22 Nov, 2016 1 commit
  4. 05 Feb, 2015 1 commit
  5. 09 Feb, 2014 1 commit
    • Matthias Clasen's avatar
      Docs: Drop entities, switch away from sgml mode · 35066ed6
      Matthias Clasen authored
      Since all element markup is now gone from the doc comments,
      we can turn off the gtk-doc sgml mode, which means that from
      now on, docbook markup is no longer allowed in doc comments.
      
      To make this possible, we have to replace all remaining
      entities in doc comments by their replacement text, & -> &
      and so on.
      35066ed6
  6. 06 Feb, 2014 2 commits
  7. 27 Nov, 2013 1 commit
  8. 24 Jun, 2013 2 commits
  9. 12 Dec, 2012 1 commit
    • Dan Winship's avatar
      Add gnetworking.h · b377e696
      Dan Winship authored
      Install a public "gnetworking.h" header that can be used to include
      the relevant OS-dependent networking headers. This does not really
      abstract away unix-vs-windows however; error codes, in particular,
      are incompatible.
      
      gnetworkingprivate.h now contains just a few internal URI-related
      functions
      
      Also add a g_networking_init() function to gnetworking.h, which can be
      used to explicitly initialize OS-level networking, rather than having
      that happen as a side-effect of registering GInetAddress.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=623187
      b377e696
  10. 14 Jun, 2011 1 commit
  11. 03 May, 2011 1 commit
    • Dan Winship's avatar
      Fix usage of _GNU_SOURCE · e56498ee
      Dan Winship authored
      _GNU_SOURCE must be defined before including any other (system)
      header, so defining it in glib-unix.h (and hoping no one has included
      anything else before that) is wrong. And the "#define _USE_GNU"
      workaround for this problem in gnetworkingprivate.h is even wronger
      (and still prone to failure anyway due to single-include guards).
      
      Fix this by defining _GNU_SOURCE in config.h when building against
      glibc. In theory this is bad because new releases of glibc may include
      symbols that conflict with glib symbols, which could then cause
      compile failures. However, most people only see new releases of glibc
      when they upgrade their distro, at which point they also generally get
      new releases of gcc, which have new warnings/errors to clean up
      anyway.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=649201
      e56498ee
  12. 01 Feb, 2011 1 commit
  13. 29 Dec, 2010 1 commit
  14. 07 Jul, 2010 1 commit
  15. 09 May, 2010 1 commit
  16. 22 Mar, 2010 1 commit
  17. 24 Nov, 2009 1 commit