1. 01 Jan, 2022 1 commit
  2. 23 Dec, 2021 2 commits
  3. 10 Dec, 2021 1 commit
  4. 01 Dec, 2021 2 commits
    • object: introduce a raw content validation function · 9f03ebd1
      Users may want to validate raw object content; provide them a function
      to do so.
      Edward Thomson committed
    • object: return GIT_EINVALID on parse errors · fc1a3f45
      Return `GIT_EINVALID` on parse errors so that direct callers of parse
      functions can determine when there was a failure to parse the object.
      
      The object parser functions will swallow this error code to prevent it
      from propagating down the chain to end-users.  (`git_merge` should not
      return `GIT_EINVALID` when a commit it tries to look up is not valid,
      this would be too vague to be useful.)
      
      The only public function that this affects is
      `git_signature_from_buffer`, which is now documented as returning
      `GIT_EINVALID` when appropriate.
      Edward Thomson committed
  5. 15 Nov, 2021 1 commit
  6. 08 Nov, 2021 3 commits
  7. 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
  8. 13 Oct, 2021 1 commit
  9. 26 Sep, 2021 1 commit
  10. 25 Sep, 2021 1 commit
    • repository: improve `hashfile` for absolute paths · 0f4256b8
      When `git_repository_hashfile` is handed an absolute path, it determines
      whether the path is within the repository's working directory or not.
      This is necessary when there is no `as_path` specified.
      
      If the path is within the working directory, then the given path should
      be used for attribute lookups (it is the effective `as_path`).  If it is
      not within the working directory, then it is _not_ eligible.
      
      Importantly, now we will _never_ pass an absolute path down to attribute
      lookup functions.
      Edward Thomson committed
  11. 22 Sep, 2021 2 commits
  12. 21 Sep, 2021 1 commit
  13. 18 Sep, 2021 5 commits
  14. 09 Sep, 2021 1 commit
  15. 05 Sep, 2021 1 commit
  16. 04 Sep, 2021 1 commit
    • common: support custom repository extensions · a24e656a
      Allow users to specify additional repository extensions that they want
      to support.  For example, callers can specify that they support
      `preciousObjects` and then may open repositories that support
      `extensions.preciousObjects`.
      
      Similarly, callers may opt out of supporting extensions that the library
      itself supports.
      Edward Thomson committed
  17. 31 Aug, 2021 1 commit
  18. 30 Aug, 2021 3 commits
  19. 29 Aug, 2021 6 commits
  20. 27 Aug, 2021 4 commits
  21. 26 Aug, 2021 1 commit