1. 09 Nov, 2021 1 commit
  2. 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
  3. 08 Aug, 2021 1 commit
  4. 20 Jul, 2019 1 commit
  5. 13 Jul, 2018 1 commit
    • treewide: remove use of C++ style comments · 9994cd3f
      C++ style comment ("//") are not specified by the ISO C90 standard and
      thus do not conform to it. While libgit2 aims to conform to C90, we did
      not enforce it until now, which is why quite a lot of these
      non-conforming comments have snuck into our codebase. Do a tree-wide
      conversion of all C++ style comments to the supported C style comments
      to allow us enforcing strict C90 compliance in a later commit.
      Patrick Steinhardt committed
  6. 10 Jun, 2018 1 commit
  7. 14 Feb, 2015 1 commit
    • merge: lock the index at the start of the merge · 8b0ddd5d
      Always lock the index when we begin the merge, before we write
      any of the metdata files.  This prevents a race where another
      client may run a commit after we have written the MERGE_HEAD but
      before we have updated the index, which will produce a merge
      commit that is treesame to one parent.  The merge will finish and
      update the index and the resultant commit would not be a merge at
      all.
      Edward Thomson committed
  8. 13 Feb, 2015 1 commit
  9. 27 Oct, 2014 1 commit
  10. 31 Mar, 2014 1 commit
  11. 20 Mar, 2014 3 commits
  12. 25 Jan, 2014 1 commit
  13. 14 Nov, 2013 1 commit
  14. 13 Nov, 2013 1 commit
  15. 05 Nov, 2013 2 commits
  16. 17 May, 2013 1 commit
  17. 30 Apr, 2013 1 commit
  18. 04 Jan, 2013 2 commits
  19. 03 Jan, 2013 1 commit