1. 23 Mar, 2022 5 commits
  2. 23 Feb, 2022 2 commits
  3. 02 Oct, 2021 1 commit
  4. 27 Nov, 2020 1 commit
  5. 11 Oct, 2020 1 commit
  6. 18 Jul, 2019 1 commit
    • sha1: win32: fix compilation due to unknown type · 7574564e
      In commit bbf034ab (hash: move `git_hash_prov` into Win32 backend,
      2019-02-22), the `git_hash_prov`'s structure name has been removed in
      favour of its typedef'ed name. But as we have no CI that compiles with
      the WinHTTPS hashing backend right now, it wasn't noticed that the
      implementation that uses this struct wasn't changed correctly.
      
      Fix the struct type to make it compile again.
      Patrick Steinhardt committed
  7. 24 Jun, 2019 4 commits
    • hash: move SHA1 implementations to its own hashing context · 8832172e
      Create a separate `git_hash_sha1_ctx` structure that is specific
      to the SHA1 implementation and move all SHA1 functions over to
      use that one instead of the generic `git_hash_ctx`. The
      `git_hash_ctx` for now simply has a union containing this single
      SHA1 implementation, only, without any mechanism to distinguish
      between different algortihms.
      Patrick Steinhardt committed
    • hash: split into generic and SHA1-specific interface · d46d3b53
      As a preparatory step to allow multiple hashing APIs to exist at
      the same time, split the hashing functions into one layer for generic
      hashing and one layer for SHA1-specific hashing. Right now, this is
      simply an additional indirection layer that doesn't yet serve any
      purpose. In the future, the generic API will be extended to allow for
      choosing which hash to use, though, by simply passing an enum to the
      hash context initialization function. This is necessary as a first step
      to be ready for Git's move to SHA256.
      Patrick Steinhardt committed
    • hash: move SHA1 implementations into 'sha1/' folder · fda20622
      As we will include additional hash algorithms in the future due
      to upstream git discussing a move away from SHA1, we should
      accomodate for that and prepare for the move. As a first step,
      move all SHA1 implementations into a common subdirectory.
      
      Also, create a SHA1-specific header file that lives inside the
      hash folder. This header will contain the SHA1-specific header
      includes, function declarations and the SHA1 context structure.
      Patrick Steinhardt committed
    • hash: introduce source files to break include circles · bd48bf3f
      The hash source files have circular include dependencies right
      now, which shows by our broken generic hash implementation. The
      "hash.h" header declares two functions and the `git_hash_ctx`
      typedef before actually including the hash backend header and can
      only declare the remaining hash functions after the include due
      to possibly static function declarations inside of the
      implementation includes.
      
      Let's break this cycle and help maintainability by creating a
      real implementation file for each of the hash implementations.
      Instead of relying on the exact include order, we now especially
      avoid the use of `GIT_INLINE` for function declarations.
      Patrick Steinhardt committed
  8. 04 Apr, 2019 1 commit
  9. 23 Mar, 2019 1 commit
  10. 22 Jan, 2019 1 commit
  11. 09 Feb, 2018 2 commits
  12. 20 Dec, 2017 1 commit
  13. 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
  14. 08 Nov, 2014 1 commit
  15. 17 Sep, 2013 1 commit
    • Add simple global shutdown hooks · a3aa5f4d
      Increasingly there are a number of components that want to do some
      cleanup at global shutdown time (at least if there are not going
      to be memory leaks).  This creates a very simple system of shutdown
      hooks that will be invoked by git_threads_shutdown.  Right now, the
      maximum number of hooks is hardcoded, but since adding a hook is
      not a public API, it should be fine and I thought it was better to
      start off with really simple code.
      Russell Belfer committed
  16. 28 Aug, 2013 1 commit
  17. 26 Aug, 2013 1 commit
  18. 26 Feb, 2013 1 commit
  19. 25 Feb, 2013 1 commit
  20. 08 Jan, 2013 1 commit
  21. 27 Nov, 2012 1 commit
  22. 13 Nov, 2012 4 commits