1. 10 Dec, 2019 1 commit
  2. 04 Dec, 2019 2 commits
  3. 13 Sep, 2019 1 commit
  4. 13 Aug, 2019 1 commit
  5. 14 Jun, 2019 1 commit
    • cmake: Modulize our TLS & hash detection · 94fc83b6
      The interactions between `USE_HTTPS` and `SHA1_BACKEND` have been
      streamlined. Previously we would have accepted not quite working
      configurations (like, `-DUSE_HTTPS=OFF -DSHA1_BACKEND=OpenSSL`) and, as
      the OpenSSL detection only ran with `USE_HTTPS`, the link would fail.
      
      The detection was moved to a new `USE_SHA1`, modeled after `USE_HTTPS`,
      which takes the values "CollisionDetection/Backend/Generic", to better
      match how the "hashing backend" is selected, the default (ON) being
      "CollisionDetection".
      
      Note that, as `SHA1_BACKEND` is still used internally, you might need to
      check what customization you're using it for.
      Etienne Samson committed
  6. 13 Jun, 2019 1 commit
    • http-parser: use our bundled http-parser by default · fb529a01
      Our bundled http-parser includes bugfixes, therefore we should prefer
      our http-parser until such time as we can identify that the system
      http-parser has these bugfixes (using a version check).
      
      Since these bugs are - at present - minor, retain the ability for users
      to force that they want to use the system http-parser anyway.  This does
      change the cmake specification so that people _must_ opt-in to the new
      behavior knowingly.
      Edward Thomson committed
  7. 27 Feb, 2019 2 commits
  8. 07 Feb, 2019 1 commit
  9. 31 Jan, 2019 1 commit
  10. 28 Jan, 2019 1 commit
  11. 25 Jan, 2019 1 commit
  12. 24 Jan, 2019 1 commit
    • index: preserve extension parsing errors · 0bf7e043
      Previously, we would clobber any extension-specific error message with
      an "extension is truncated" message. This makes `read_extension`
      correctly preserve those errors, takes responsibility for truncation
      errors, and adds a new message with the actual extension signature for
      unsupported mandatory extensions.
      Etienne Samson committed
  13. 22 Jan, 2019 1 commit
  14. 17 Jan, 2019 6 commits
  15. 19 Oct, 2018 1 commit
  16. 30 Aug, 2018 1 commit
    • docs: clarify and include licenses of dependencies · 2e0f926e
      While our contribution guide tries to make clear the licenses that apply
      to libgit2, it does not make clear that different licenses apply to our
      bundled dependencies. Make this clear by listing each dependency
      together with the licenses that they are governed by. Furthermore,
      bundle the complete license texts next to the code they apply to.
      Patrick Steinhardt committed
  17. 27 Aug, 2018 1 commit
  18. 20 Aug, 2018 2 commits
  19. 03 Aug, 2018 3 commits
  20. 29 Jun, 2018 1 commit
  21. 12 Jun, 2018 1 commit
  22. 09 Jun, 2018 1 commit
  23. 30 May, 2018 1 commit
    • docs: reorganize documents · 68a3c0b1
      Our non-technical documents are currently floating around loosely in our
      project's root, making it harden than necessary to discover what one is
      searching for. We do have a "docs/" directory, though, which serves
      exactly that purpose of hosting documentation.
      
      Move our non-technical documentation into the "docs/" directory. Adjust
      all links to these documents.
      Patrick Steinhardt committed
  24. 21 May, 2018 1 commit
  25. 02 May, 2018 1 commit
  26. 30 Mar, 2018 1 commit
  27. 20 Feb, 2018 1 commit
  28. 15 Feb, 2018 1 commit
  29. 27 Jan, 2018 1 commit
  30. 19 Jan, 2018 1 commit