1. 08 Jun, 2017 1 commit
    • settings: rename `GIT_OPT_ENABLE_SYNCHRONOUS_OBJECT_CREATION` · 6c23704d
      Initially, the setting has been solely used to enable the use of
      `fsync()` when creating objects. Since then, the use has been extended
      to also cover references and index files. As the option is not yet part
      of any release, we can still correct this by renaming the option to
      something more sensible, indicating not only correlation to objects.
      
      This commit renames the option to `GIT_OPT_ENABLE_FSYNC_GITDIR`. We also
      move the variable from the object to repository source code.
      Patrick Steinhardt committed
  2. 28 Apr, 2017 1 commit
    • odb: add option to turn off hash verification · 35079f50
      Verifying hashsums of objects we are reading from the ODB may be costly
      as we have to perform an additional hashsum calculation on the object.
      Especially when reading large objects, the penalty can be as high as
      35%, as can be seen when executing the equivalent of `git cat-file` with
      and without verification enabled. To mitigate for this, we add a global
      option for libgit2 which enables the developer to turn off the
      verification, e.g. when he can be reasonably sure that the objects on
      disk won't be corrupted.
      Patrick Steinhardt committed
  3. 25 Apr, 2017 1 commit
  4. 03 Apr, 2017 1 commit
  5. 28 Feb, 2017 2 commits
  6. 10 Feb, 2017 1 commit
  7. 21 Jan, 2017 1 commit
  8. 29 Dec, 2016 1 commit
  9. 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
  10. 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
  11. 06 Jul, 2016 1 commit
  12. 05 Jul, 2016 1 commit
  13. 21 Jun, 2016 1 commit
  14. 14 Mar, 2016 2 commits
  15. 28 Feb, 2016 1 commit
  16. 23 Feb, 2016 1 commit
  17. 17 Nov, 2015 1 commit
  18. 12 Nov, 2015 1 commit
  19. 19 Sep, 2015 1 commit
  20. 23 Apr, 2015 2 commits
  21. 01 Oct, 2014 1 commit
  22. 24 Mar, 2014 1 commit
  23. 03 Mar, 2014 2 commits
  24. 25 Feb, 2014 2 commits
  25. 15 Jan, 2014 1 commit