1. 30 Aug, 2023 2 commits
  2. 13 May, 2023 2 commits
    • net: move `gitno` buffer to `staticstr` · 11c89c38
      The `gitno` buffer interface is another layer on top of socket reads.
      Abstract it a bit into a "static string" that has `git_str` like
      semantics but without heap allocation which moves the actual reading
      logic into the socket / stream code, and allows for easier future usage
      of a static / stack-allocated `git_str`-like interface.
      Edward Thomson committed
    • util: make monotonic time fn return ms · 6c0d5b11
      `git__timer` is now `git_time_monotonic`, and returns milliseconds
      since an arbitrary epoch.
      
      Using a floating point to store the number of seconds elapsed was
      clever, as it better supports the wide range of precision from the
      different monotonic clocks of different systems. But we're a version
      control system, not a real-time clock.
      
      Milliseconds is a good enough precision for our work _and_ it's the
      units that system calls like `poll` take and that our users interact
      with.
      
      Make `git_time_monotonic` return the monotonically increasing number
      of milliseconds "ticked" since some arbitrary epoch.
      Edward Thomson committed
  3. 09 May, 2023 1 commit
  4. 08 May, 2023 1 commit
  5. 25 Apr, 2023 1 commit
  6. 10 Mar, 2023 1 commit
  7. 12 Feb, 2023 2 commits
  8. 25 Nov, 2022 1 commit
    • transport: fix capabilities calculation · be7356d0
      This looks like a typo to me, from what i can see these lines were
      added at the same time and because of how capabilities are calculated,
      it's likely that this code will work in situations where these
      capabilities were the last ones.
      Russell Sim committed
  9. 01 Aug, 2022 1 commit
  10. 29 Jul, 2022 1 commit
  11. 15 Jun, 2022 1 commit
  12. 23 Feb, 2022 1 commit
  13. 08 Feb, 2022 1 commit
  14. 07 Feb, 2022 1 commit
    • push: Prepare pack before sending pack header. · 19ec5923
      For large pushes, preparing the pack can take a while. Currently we
      send the pack header first, followed by preparing the pack and then
      finally sending the pack. Unfortunately github.com will terminate
      a git-receive-pack command over http if it is idle for more than 10
      seconds. This is easily exceeded for a large push, and so the push is
      rejected with a Broken Pipe error.
      
      This patch moves the pack preparation ahead of sending the pack header,
      so that the timeout is avoided.
      
      prepare_pack() can be called multiple times but will only do the work
      once, so the original PREPARE_PACK call inside git_packbuilder_foreach()
      remains.
      Colin Stolley committed
  15. 06 Feb, 2022 1 commit
  16. 30 Jan, 2022 1 commit
  17. 06 Jan, 2022 1 commit
    • 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
  18. 05 Jan, 2022 1 commit
  19. 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
  20. 15 Jul, 2021 1 commit
  21. 06 Dec, 2020 1 commit
  22. 27 Nov, 2020 1 commit
  23. 24 Jan, 2020 1 commit
  24. 23 Aug, 2019 1 commit
  25. 21 Aug, 2019 1 commit
    • smart: use push_glob instead of manual filtering · 39d18fe6
      The code worked under the assumption that anything under `refs/tags` are
      tag objects, and all the rest would be peelable to a commit. As it is
      completely valid to have tags to blobs under a non `refs/tags` ref, this
      would cause failures when trying to peel a tag to a commit.
      
      Fix the broken filtering by switching to `git_revwalk_push_glob`, which
      already handles this case.
      Etienne Samson committed
  26. 24 Jun, 2019 1 commit
  27. 15 Jun, 2019 1 commit
  28. 22 Feb, 2019 2 commits
  29. 22 Jan, 2019 1 commit
  30. 17 Jan, 2019 1 commit
  31. 03 Oct, 2018 1 commit
  32. 06 Jul, 2018 1 commit
  33. 29 Jun, 2018 2 commits
  34. 26 Jun, 2018 1 commit
  35. 25 Jun, 2018 1 commit