1. 28 Feb, 2017 2 commits
  2. 10 Feb, 2017 1 commit
  3. 21 Jan, 2017 1 commit
  4. 29 Dec, 2016 1 commit
  5. 17 Dec, 2016 1 commit
    • settings: don't hard-code HTTPS capability · 061a0ad1
      This partially reverts bdec62dc which activates
      the transport code-paths which allow you to use a custom TLS implementation
      without having to have one at build-time.
      
      However the capabilities describe how libgit2 was built, not what it could
      potentially support, bring back the ifdefs so we only say we support HTTPS if
      libgit2 was itself built with a TLS implementation.
      Carlos Martín Nieto committed
  6. 27 Aug, 2016 1 commit
    • Make symbolic ref target validation optional · 452bf57c
      Introduce GIT_OPT_ENABLE_SYMBOLIC_REF_TARGET_VALIDATION option.
      Setting this option to 0 allows
      validation of a symbolic ref's target to be bypassed.
      This option is enabled by default.
      
      This mechanism is added primarily to address a discrepancy between git
      behaviour and libgit2 behaviour, whereby the former allows the symbolic
      ref target to carry an arbitrary string and the latter does not, so:
      
          $ git symbolic-ref refs/heads/foo bar
          $ cat .git/refs/heads/foo
          ref: bar
      
      where as attempting the same via libgit2 raises an error:
      
          The given reference name 'bar' is not valid
      
      this mechanism also allows those that might want to make use of
      git's more lenient treatment of symbolic ref targets to do so.
      Richard Ipsum committed
  7. 06 Jul, 2016 1 commit
  8. 05 Jul, 2016 1 commit
  9. 21 Jun, 2016 1 commit
  10. 14 Mar, 2016 2 commits
  11. 28 Feb, 2016 1 commit
  12. 23 Feb, 2016 1 commit
  13. 17 Nov, 2015 1 commit
  14. 12 Nov, 2015 1 commit
  15. 19 Sep, 2015 1 commit
  16. 23 Apr, 2015 2 commits
  17. 01 Oct, 2014 1 commit
  18. 24 Mar, 2014 1 commit
  19. 03 Mar, 2014 2 commits
  20. 25 Feb, 2014 2 commits
  21. 15 Jan, 2014 1 commit