1. 20 May, 2019 1 kayıt (commit)
  2. 15 May, 2019 1 kayıt (commit)
  3. 13 May, 2019 1 kayıt (commit)
  4. 12 May, 2019 1 kayıt (commit)
  5. 10 May, 2019 1 kayıt (commit)
  6. 09 May, 2019 3 kayıt (commit)
  7. 08 May, 2019 1 kayıt (commit)
  8. 07 May, 2019 2 kayıt (commit)
  9. 02 May, 2019 1 kayıt (commit)
  10. 29 Nis, 2019 2 kayıt (commit)
  11. 21 Nis, 2019 1 kayıt (commit)
    • Mike Kaganski's avatar
      Properly initialize gpgme-w32spawn.exe path on Windows · cca68302
      Mike Kaganski yazdı
      On Windows, gpgme expects gpgme-w32spawn.exe to be in the same directory as the current
      process executable. This assumption might be wrong, e.g., for bundled python, which is
      in instdir/program/python-core-x.y.z/bin, while gpgme-w32spawn.exe is in instdir/program.
      In this case, if an operation in a python script requires initializing gpgme, it will be
      interrupted by a modal warning box telling that gpgme-w32spawn.exe was not found.
      
      If we can't find gpgme-w32spawn.exe in the current executable location, then try to find
      the spawn executable, and inform gpgme about actual location using gpgme_set_global_flag.
      
      Change-Id: Ie30a0d4a6666767e8c54f1bdc67b67570d6ea47a
      Reviewed-on: https://gerrit.libreoffice.org/71014
      Tested-by: Jenkins
      Reviewed-by: 's avatarMike Kaganski <mike.kaganski@collabora.com>
      cca68302
  12. 15 Nis, 2019 2 kayıt (commit)
  13. 13 Nis, 2019 1 kayıt (commit)
  14. 09 Nis, 2019 1 kayıt (commit)
  15. 01 Nis, 2019 1 kayıt (commit)
  16. 16 Mar, 2019 2 kayıt (commit)
  17. 07 Mar, 2019 2 kayıt (commit)
  18. 05 Mar, 2019 1 kayıt (commit)
  19. 27 Şub, 2019 1 kayıt (commit)
  20. 26 Şub, 2019 1 kayıt (commit)
  21. 25 Şub, 2019 1 kayıt (commit)
  22. 21 Şub, 2019 1 kayıt (commit)
  23. 19 Şub, 2019 1 kayıt (commit)
  24. 14 Şub, 2019 5 kayıt (commit)
  25. 13 Şub, 2019 2 kayıt (commit)
  26. 12 Şub, 2019 1 kayıt (commit)
  27. 11 Şub, 2019 1 kayıt (commit)
  28. 05 Şub, 2019 1 kayıt (commit)