1. 27 Nov, 2020 1 commit
  2. 06 Oct, 2020 1 commit
  3. 03 Aug, 2020 2 commits
  4. 09 Jun, 2020 1 commit
    • tree-wide: do not compile deprecated functions with hard deprecation · c6184f0c
      When compiling libgit2 with -DDEPRECATE_HARD, we add a preprocessor
      definition `GIT_DEPRECATE_HARD` which causes the "git2/deprecated.h"
      header to be empty. As a result, no function declarations are made
      available to callers, but the implementations are still available to
      link against. This has the problem that function declarations also
      aren't visible to the implementations, meaning that the symbol's
      visibility will not be set up correctly. As a result, the resulting
      library may not expose those deprecated symbols at all on some platforms
      and thus cause linking errors.
      
      Fix the issue by conditionally compiling deprecated functions, only.
      While it becomes impossible to link against such a library in case one
      uses deprecated functions, distributors of libgit2 aren't expected to
      pass -DDEPRECATE_HARD anyway. Instead, users of libgit2 should manually
      define GIT_DEPRECATE_HARD to hide deprecated functions. Using "real"
      hard deprecation still makes sense in the context of CI to test we don't
      use deprecated symbols ourselves and in case a dependant uses libgit2 in
      a vendored way and knows it won't ever use any of the deprecated symbols
      anyway.
      Patrick Steinhardt committed
  5. 06 Nov, 2019 1 commit
  6. 17 Oct, 2019 1 commit
  7. 20 Jul, 2019 1 commit
  8. 14 Jun, 2019 1 commit
    • Rename opt init functions to `options_init` · 0b5ba0d7
      In libgit2 nomenclature, when we need to verb a direct object, we name
      a function `git_directobject_verb`.  Thus, if we need to init an options
      structure named `git_foo_options`, then the name of the function that
      does that should be `git_foo_options_init`.
      
      The previous names of `git_foo_init_options` is close - it _sounds_ as
      if it's initializing the options of a `foo`, but in fact
      `git_foo_options` is its own noun that should be respected.
      
      Deprecate the old names; they'll now call directly to the new ones.
      Edward Thomson committed
  9. 22 Jan, 2019 1 commit
  10. 10 Jun, 2018 1 commit
  11. 03 Jul, 2017 1 commit
    • Make sure to always include "common.h" first · 0c7f49dd
      Next to including several files, our "common.h" header also declares
      various macros which are then used throughout the project. As such, we
      have to make sure to always include this file first in all
      implementation files. Otherwise, we might encounter problems or even
      silent behavioural differences due to macros or defines not being
      defined as they should be. So in fact, our header and implementation
      files should make sure to always include "common.h" first.
      
      This commit does so by establishing a common include pattern. Header
      files inside of "src" will now always include "common.h" as its first
      other file, separated by a newline from all the other includes to make
      it stand out as special. There are two cases for the implementation
      files. If they do have a matching header file, they will always include
      this one first, leading to "common.h" being transitively included as
      first file. If they do not have a matching header file, they instead
      include "common.h" as first file themselves.
      
      This fixes the outlined problems and will become our standard practice
      for header and source files inside of the "src/" from now on.
      Patrick Steinhardt committed
  12. 13 Feb, 2017 1 commit
    • repository: use `git_repository_item_path` · c5f3da96
      The recent introduction of the commondir variable of a repository
      requires callers to distinguish whether their files are part of
      the dot-git directory or the common directory shared between
      multpile worktrees. In order to take the burden from callers and
      unify knowledge on which files reside where, the
      `git_repository_item_path` function has been introduced which
      encapsulate this knowledge.
      
      Modify most existing callers of `git_repository_path` to use
      `git_repository_item_path` instead, thus making them implicitly
      aware of the common directory.
      Patrick Steinhardt committed
  13. 21 Jun, 2016 1 commit
  14. 03 Aug, 2015 1 commit
  15. 01 Jun, 2015 1 commit
    • clone: fall back to copying when linking does not work · 10940736
      We use heuristics to make a decent guess at when we can save time and
      space by linking object files during a clone. Unfortunately checking the
      device id isn't enough, as those would be the same during e.g. a bind-mount,
      but the OS still does not allow us to link between mounts of the same
      filesystem.
      
      If we fail to perform the links, fall back to copying the contents into
      a new file as a last attempt.
      Carlos Martín Nieto committed
  16. 13 May, 2015 4 commits
  17. 03 Mar, 2015 3 commits
  18. 30 Sep, 2014 1 commit
  19. 02 Sep, 2014 2 commits
  20. 29 Aug, 2014 1 commit
  21. 05 Aug, 2014 1 commit
  22. 16 Jul, 2014 1 commit
  23. 11 Jul, 2014 1 commit
  24. 02 Jul, 2014 2 commits
  25. 27 Jun, 2014 1 commit
  26. 03 Jun, 2014 1 commit
  27. 28 May, 2014 5 commits
  28. 22 May, 2014 1 commit