1. 14 Jul, 2022 1 commit
  2. 20 Jun, 2022 1 commit
  3. 15 Jun, 2022 1 commit
  4. 10 Apr, 2022 1 commit
  5. 23 Mar, 2022 1 commit
  6. 23 Feb, 2022 1 commit
  7. 21 Feb, 2022 1 commit
  8. 06 Feb, 2022 3 commits
  9. 05 Feb, 2022 2 commits
  10. 13 Jan, 2022 2 commits
  11. 06 Jan, 2022 2 commits
    • remote: introduce `git_remote_connect_options` · 6fc6eeb6
      The existing mechanism for providing options to remote fetch/push calls,
      and subsequently to transports, is unsatisfactory.  It requires an
      options structure to avoid breaking the API and callback signatures.
      
      1. Introduce `git_remote_connect_options` to satisfy those needs.
      
      2. Add a new remote connection API, `git_remote_connect_ext` that will
         take this new options structure.  Existing `git_remote_connect` calls
         will proxy to that.  `git_remote_fetch` and `git_remote_push` will
         proxy their fetch/push options to that as well.
      
      3. Define the interaction between `git_remote_connect` and fetch/push.
         Connect _may_ be called before fetch/push, but _need not_ be.  The
         semantics of which options would be used for these operations was
         not specified if you specify options for both connect _and_ fetch.
         Now these are defined that the fetch or push options will be used
         _if_ they were specified.  Otherwise, the connect options will be
         used if they were specified.  Otherwise, the library's defaults will
         be used.
      
      4. Update the transports to understand `git_remote_connect_options`.
         This is a breaking change to the systems API.
      Edward Thomson committed
    • remote: improved error reporting · f99a0d69
      Several places in the remote code identify an error and then swallow it;
      return the error.
      Edward Thomson committed
  12. 24 Dec, 2021 1 commit
  13. 11 Nov, 2021 2 commits
  14. 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
  15. 18 Sep, 2021 2 commits
  16. 16 Sep, 2021 1 commit
  17. 09 Sep, 2021 1 commit
  18. 02 Sep, 2021 2 commits
  19. 29 Aug, 2021 2 commits
  20. 27 Aug, 2021 1 commit
  21. 05 Aug, 2021 1 commit
  22. 11 Jun, 2021 1 commit
  23. 15 Feb, 2021 1 commit
  24. 07 Jan, 2021 1 commit
  25. 27 Nov, 2020 1 commit
  26. 25 Nov, 2020 1 commit
  27. 25 Oct, 2020 5 commits