1. 21 Dec, 2020 1 commit
  2. 18 Dec, 2020 1 commit
  3. 09 Dec, 2020 1 commit
  4. 23 Jun, 2020 1 commit
  5. 12 Jun, 2020 1 commit
  6. 04 Mar, 2020 1 commit
  7. 25 Sep, 2019 1 commit
  8. 29 Jul, 2019 5 commits
  9. 08 May, 2019 1 commit
  10. 28 Jan, 2019 1 commit
    • Emmanuel Fleury's avatar
      Fixing signedness in glib/gdate.c · 6e49b36c
      Emmanuel Fleury authored
      glib/gdate.c: In function ‘g_date_add_months’:
      glib/gdate.c:1732:27: error: comparison of integer expressions of different signedness: ‘guint’ {aka ‘unsigned int’} and ‘int’ [-Werror=sign-compare]
         g_return_if_fail (years <= G_MAXUINT16 - d->year);
                                 ^~
      glib/gmacros.h:455:25: note: in definition of macro ‘G_LIKELY’
       #define G_LIKELY(expr) (expr)
                               ^~~~
      glib/gdate.c:1732:3: note: in expansion of macro ‘g_return_if_fail’
         g_return_if_fail (years <= G_MAXUINT16 - d->year);
         ^~~~~~~~~~~~~~~~
      glib/gdate.c: In function ‘g_date_add_years’:
      glib/gdate.c:1816:28: error: comparison of integer expressions of different signedness: ‘guint’ {aka ‘unsigned int’} and ‘int’ [-Werror=sign-compare]
         g_return_if_fail (nyears <= G_MAXUINT16 - d->year);
                                  ^~
      glib/gmacros.h:455:25: note: in definition of macro ‘G_LIKELY’
       #define G_LIKELY(expr) (expr)
                               ^~~~
      glib/gdate.c:1816:3: note: in expansion of macro ‘g_return_if_fail’
         g_return_if_fail (nyears <= G_MAXUINT16 - d->year);
         ^~~~~~~~~~~~~~~~
      6e49b36c
  11. 13 Nov, 2018 1 commit
  12. 29 Oct, 2018 1 commit
  13. 04 Sep, 2018 1 commit
    • Iain Lane's avatar
      Document that GTimeVal is subject to the year 2038 problem on 32-bit systems · 68a4e273
      Iain Lane authored
      It might not be immediately obvious that this is the case. Let's record
      it in the description of `GTimeVal` itself and also in
      `g_time_val_from_iso8601`.
      
      We also drop an incorrect statement in the documentation for
      `g_time_val_from_iso8601` stating that years up to 3000 were supported;
      this is also not true for the same reason.
      
      Related: #1509
      68a4e273
  14. 09 Jul, 2018 1 commit
  15. 29 May, 2018 1 commit
  16. 27 Apr, 2018 1 commit
  17. 13 Apr, 2018 3 commits
  18. 28 Feb, 2018 1 commit
  19. 20 Feb, 2018 3 commits
  20. 11 Oct, 2017 1 commit
  21. 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
  22. 07 Apr, 2016 1 commit
  23. 03 Mar, 2016 1 commit
  24. 08 Feb, 2016 1 commit
  25. 07 Nov, 2015 1 commit
    • Philip Withnall's avatar
      glib: Add missing (nullable) and (optional) annotations · 25a7c817
      Philip Withnall authored
      Add various (nullable) and (optional) annotations which were missing
      from a variety of functions. Also port a couple of existing (allow-none)
      annotations in the same files to use (nullable) and (optional) as
      appropriate instead.
      
      Secondly, add various (not nullable) annotations as needed by the new
      default in gobject-introspection of marking gpointers as (nullable). See
      https://bugzilla.gnome.org/show_bug.cgi?id=729660.
      
      This includes adding some stub documentation comments for the
      assertion macro error functions, which weren’t previously documented.
      The new comments are purely to allow for annotations, and hence are
      marked as (skip) to prevent the symbols appearing in the GIR file.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=719966
      25a7c817
  26. 05 Jun, 2015 1 commit
  27. 08 Feb, 2014 1 commit
  28. 01 Feb, 2014 3 commits
  29. 31 Jan, 2014 2 commits