1. 13 Aug, 2019 1 commit
  2. 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
  3. 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
  4. 31 Jan, 2019 1 commit
  5. 25 Jan, 2019 1 commit
  6. 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
  7. 17 Jan, 2019 6 commits
  8. 29 Jun, 2018 1 commit
  9. 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
  10. 29 May, 2018 1 commit
  11. 17 Apr, 2018 2 commits
  12. 26 Mar, 2018 1 commit
  13. 02 Mar, 2018 1 commit
  14. 20 Feb, 2018 2 commits
  15. 09 Feb, 2018 2 commits
  16. 21 Jan, 2018 1 commit
  17. 19 Nov, 2017 1 commit
  18. 04 Nov, 2017 1 commit
  19. 30 Oct, 2017 1 commit
  20. 30 Jul, 2017 1 commit
  21. 26 Jul, 2017 1 commit
  22. 14 Jun, 2017 1 commit
  23. 11 Jun, 2017 2 commits
  24. 09 Jun, 2017 1 commit
  25. 05 May, 2017 1 commit
    • remote: add function to create detached remotes · 4bc16c37
      Right now it is only possible to create remotes from a repository. While
      this is probably the most common use-case, there are commands which make
      sense even without a repository, e.g. the equivalence of `git
      ls-remote`. Add a new function `git_remote_create_detached`, which
      simply accepts a URL.
      Eric Myhre committed
  26. 03 Apr, 2017 1 commit
  27. 21 Jan, 2017 1 commit
  28. 14 Jan, 2017 1 commit
  29. 03 Jan, 2017 2 commits
  30. 15 Nov, 2016 1 commit