1. 12 Feb, 2023 1 commit
  2. 14 Jul, 2022 1 commit
  3. 20 Jun, 2022 3 commits
  4. 15 Jun, 2022 1 commit
  5. 10 Apr, 2022 1 commit
  6. 05 Apr, 2022 1 commit
    • [midx] Fix an undefined behavior (left-shift signed overflow) · 33b1d3fd
      There was a missing check to ensure that the `off64_t` (which is a
      signed value) didn't overflow when parsing it from the midx file. This
      shouldn't have huge repercusions since the parsed value is immediately
      validated afterwards, but then again, there is no such thing as "benign"
      undefined behavior.
      
      This change makes all the bitwise arithmetic happen with unsigned types
      and is only casted to `off64_t` until the very end.
      
      Thanks to Taotao Gu for finding and reporting this!
      lhchavez committed
  7. 23 Feb, 2022 1 commit
  8. 28 Jan, 2022 1 commit
  9. 14 Nov, 2021 1 commit
  10. 11 Nov, 2021 3 commits
  11. 09 Nov, 2021 1 commit
  12. 28 Oct, 2021 1 commit
  13. 18 Oct, 2021 1 commit
  14. 17 Oct, 2021 2 commits
    • cmake: BUILD_CLAR is now BUILD_TESTS · 4e14d4c6
      Nobody knows what CLAR is.  The test building option should be
      `BUILD_TESTS`.
      Edward Thomson committed
    • 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
  15. 02 Oct, 2021 1 commit
  16. 10 Mar, 2021 1 commit
    • commit-graph: Create `git_commit_graph` as an abstraction for the file · 25b75cd9
      This change does a medium-size refactor of the git_commit_graph_file and
      the interaction with the ODB. Now instead of the ODB owning a direct
      reference to the git_commit_graph_file, there will be an intermediate
      git_commit_graph. The main advantage of that is that now end users can
      explicitly set a git_commit_graph that is eagerly checked for errors,
      while still being able to lazily use the commit-graph in a regular ODB,
      if the file is present.
      lhchavez committed
  17. 10 Jan, 2021 2 commits
  18. 05 Oct, 2020 1 commit
  19. 17 Oct, 2019 1 commit
  20. 17 Aug, 2019 1 commit
  21. 29 Jul, 2019 1 commit
  22. 20 Jul, 2019 3 commits
  23. 05 Jul, 2019 5 commits
  24. 19 May, 2019 1 commit
  25. 22 Feb, 2019 1 commit
  26. 25 Jan, 2019 1 commit
  27. 22 Jan, 2019 1 commit
  28. 17 Jan, 2019 1 commit