1. 14 Jul, 2022 1 commit
  2. 20 Jun, 2022 2 commits
  3. 15 Jun, 2022 1 commit
  4. 10 Apr, 2022 1 commit
    • tree: move git_oid into tree entry · ab042161
      A tree entry previously pointed directly into the object id within the
      tree object itself; this is useful to avoid any unnecessary memory copy
      (and an unnecessary use of 40 bytes per tree entry) but difficult if we
      change the underlying `git_oid` object to not simply be a raw object id
      but have additional structure.
      
      This commit moves the `git_oid` directly into the tree entry; this
      simplifies the tree entry creation from user data.  We now copy the
      `git_oid` into place when parsing.
      Edward Thomson committed
  5. 23 Feb, 2022 1 commit
  6. 15 Nov, 2021 1 commit
  7. 09 Nov, 2021 2 commits
  8. 17 Oct, 2021 1 commit
    • str: introduce `git_str` for internal, `git_buf` is external · f0e693b1
      libgit2 has two distinct requirements that were previously solved by
      `git_buf`.  We require:
      
      1. A general purpose string class that provides a number of utility APIs
         for manipulating data (eg, concatenating, truncating, etc).
      2. A structure that we can use to return strings to callers that they
         can take ownership of.
      
      By using a single class (`git_buf`) for both of these purposes, we have
      confused the API to the point that refactorings are difficult and
      reasoning about correctness is also difficult.
      
      Move the utility class `git_buf` to be called `git_str`: this represents
      its general purpose, as an internal string buffer class.  The name also
      is an homage to Junio Hamano ("gitstr").
      
      The public API remains `git_buf`, and has a much smaller footprint.  It
      is generally only used as an "out" param with strict requirements that
      follow the documentation.  (Exceptions exist for some legacy APIs to
      avoid breaking callers unnecessarily.)
      
      Utility functions exist to convert a user-specified `git_buf` to a
      `git_str` so that we can call internal functions, then converting it
      back again.
      Edward Thomson committed
  9. 28 Apr, 2021 1 commit
    • iterator: validate workdir paths · b457fe27
      Supply the repository for the filesystem and workdir iterators - for
      workdir iterators, this is non-null and we can lookup the core.longpaths
      configuration option.  (For regular filesystem iterators, this is NULL,
      so core.longpaths does not apply.)
      Edward Thomson committed
  10. 27 Nov, 2020 1 commit
  11. 01 Jun, 2020 1 commit
  12. 18 Jan, 2020 1 commit
  13. 27 Aug, 2019 2 commits
  14. 18 Jul, 2019 1 commit
  15. 24 Jun, 2019 2 commits
  16. 16 Apr, 2019 1 commit
  17. 25 Jan, 2019 1 commit
    • iterator: cast filesystem iterator entry values explicitly · 1d4ddb8e
      The filesystem iterator takes `stat` data from disk and puts them into
      index entries, which use 32 bit ints for time (the seconds portion) and
      filesize.  However, on most systems these are not 32 bit, thus will
      typically invoke a warning.
      
      Most users ignore these fields entirely.  Diff and checkout code do use
      the values, however only for the cache to determine if they should check
      file modification.  Thus, this is not a critical error (and will cause a
      hash recomputation at worst).
      Edward Thomson committed
  18. 22 Jan, 2019 1 commit
  19. 01 Dec, 2018 1 commit
  20. 28 Nov, 2018 1 commit
  21. 04 Nov, 2018 1 commit
  22. 03 Nov, 2018 1 commit
    • iterator: optionally hash filesystem iterators · 2b12dcf6
      Optionally hash the contents of files encountered in the filesystem or
      working directory iterators.  This is not expected to be used in
      production code paths, but may allow us to simplify some test contexts.
      
      For working directory iterators, apply filters as appropriate, since we
      have the context able to do it.
      Edward Thomson committed
  23. 10 Jun, 2018 1 commit
  24. 31 Jan, 2018 2 commits
  25. 30 Dec, 2017 1 commit
  26. 29 Dec, 2017 1 commit
  27. 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
  28. 14 Nov, 2016 1 commit
  29. 22 Aug, 2016 1 commit
  30. 21 Apr, 2016 1 commit
  31. 02 Apr, 2016 1 commit
  32. 31 Mar, 2016 3 commits
  33. 24 Mar, 2016 1 commit