1. 18 Dec, 2018 4 commits
  2. 17 Dec, 2018 7 commits
  3. 11 Dec, 2018 4 commits
    • Will Thompson's avatar
      gdbus-codegen: test --interface-info-{header,body} · 0569daeb
      Will Thompson authored
      This test is rudimentary but better than nothing.
      
      (Backport to glib-2-58: Fix minor merge conflict.)
      0569daeb
    • Will Thompson's avatar
      gdbus-codegen: sort input files · fe7b608f
      Will Thompson authored
      This means the output (including lists of filenames) does not depend on
      the order of the input files, which may matter if this tool is invoked
      with a glob or some other mechanism that doesn't guarantee an order.
      fe7b608f
    • Will Thompson's avatar
      gdbus-codegen: don't sort args in --interface-info-body · 4c4acb6f
      Will Thompson authored
      Previously, method and signal arguments were sorted by name, which
      (assuming you don't happen to give your arguments
      lexicographically-ordered names) means the generated signatures were
      incorrect when there is more than 1 argument.
      
      While sorting the methods and signals themselves (and properties, and
      annotations on all these) is fine, it's easiest to not sort anything.
      4c4acb6f
    • Will Thompson's avatar
      gdbus-codegen: make --interface-info-{header,body} not crash · 06e1d72f
      Will Thompson authored
      Since 1217b1bc, LICENSE_STR has taken two
      parameters, not one. Without this change, running either mode fails
      with a traceback like:
      
          Traceback (most recent call last):
            File "../gdbus-codegen", line 55, in <module>
              sys.exit(codegen_main.codegen_main())
            File ".../codegen_main.py", line 294, in codegen_main
              gen.generate()
            File ".../codegen.py", line 896, in generate
              self.generate_body_preamble()
            File ".../codegen.py", line 682, in generate_body_preamble
              self.outfile.write(LICENSE_STR.format(config.VERSION))
          IndexError: tuple index out of range
      
      8916874e, which introduced these flags,
      was actually merged after that commit, but I assume it was written
      beforehand.
      06e1d72f
  4. 10 Dec, 2018 2 commits
  5. 07 Dec, 2018 1 commit
  6. 02 Dec, 2018 1 commit
  7. 28 Nov, 2018 1 commit
  8. 27 Nov, 2018 6 commits
  9. 24 Nov, 2018 1 commit
  10. 23 Nov, 2018 4 commits
  11. 20 Nov, 2018 1 commit
  12. 14 Nov, 2018 2 commits
  13. 13 Nov, 2018 2 commits
    • Xavier Claessens's avatar
      Merge branch 'master' into 'master' · 68203b16
      Xavier Claessens authored
      meson: add aarch64 memory barrier handling
      
      See merge request GNOME/glib!462
      
      (cherry picked from commit a72766bb)
      
      704522c5 meson: add aarch64 memory barrier handling
      68203b16
    • Michael Catanzaro's avatar
      Update documentation of g_tls_connection_handshake() again · 8616425b
      Michael Catanzaro authored
      I made a mistake when last updating the documentation in 94a99ae9. I
      wrote that, with TLS 1.3, this would perform a rekey instead of a
      rehandshake. In fact, that's only true for client connections. For
      server connections, it's a no-op.
      
      I was a bit nervous about how to document the behavior anyway, because
      we really don't know what behavior will be reasonable with non-GnuTLS
      crypto backends. This behavior is reasonable for the GnuTLS backend, but
      might not necessarily make sense for OpenSSL. Ideally, we would
      discourage API users from doing things which could have unexpected
      effects, so instead of documenting what the GnuTLS backend does, I think
      it'd be better to document that this is "undefined but not dangerous,"
      since of course we want to make sure that existing code that doesn't
      know about TLS 1.3 is not broken.
      
      
      (cherry picked from commit 68878ab5)
      8616425b
  14. 10 Nov, 2018 1 commit
  15. 08 Nov, 2018 1 commit
  16. 07 Nov, 2018 2 commits