1. 09 May, 2022 1 commit
    • revparse: Remove error-prone, redundant test · 7f53d7b6
      Originally introduced in: 776a6a8e
      
      This test case has recently been fixed in bdab2238, but that fix will only last for a year. Next year the same problem will crop up and the test will need to be re-edited.
      
      This is not ideal as
      - This test case becomes an unnecessary burden for developers
      - Downstream distros or even just users who want to build older versions of libgit2 are guaranteed to have this test fail
      
      Furthermore, this test case is entirely unnecessary, as the functionality that was originally (see 776a6a8e) intended to be tested is well-covered by subsequent tests which specify a date instead of a "x ago" specification.
      Carl Dong committed
  2. 03 May, 2022 1 commit
  3. 23 Feb, 2022 1 commit
  4. 31 Jan, 2022 1 commit
  5. 09 Nov, 2021 1 commit
  6. 21 Oct, 2021 2 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. 31 Jan, 2021 1 commit
  9. 10 Jun, 2018 1 commit
  10. 05 May, 2017 1 commit
  11. 26 Jun, 2015 1 commit
  12. 03 Mar, 2015 2 commits
  13. 22 Nov, 2014 1 commit
    • peel: reject bad queries with EINVALIDSPEC · 753e17b0
      There are some combination of objects and target types which we know
      cannot be fulfilled. Return EINVALIDSPEC for those to signify that there
      is a mismatch in the user-provided data and what the object model is
      capable of satisfying.
      
      If we start at a tag and in the course of peeling find out that we
      cannot reach a particular type, we return EPEEL.
      Carlos Martín Nieto committed
  14. 30 Jan, 2014 2 commits
  15. 15 Jan, 2014 1 commit
  16. 14 Nov, 2013 1 commit
  17. 10 Sep, 2013 1 commit
  18. 13 Jul, 2013 1 commit
  19. 16 May, 2013 2 commits
  20. 15 May, 2013 1 commit
  21. 15 Apr, 2013 4 commits
  22. 09 Apr, 2013 1 commit
  23. 08 Apr, 2013 1 commit
  24. 07 Apr, 2013 2 commits
  25. 07 Mar, 2013 1 commit
  26. 03 Feb, 2013 2 commits
  27. 01 Dec, 2012 2 commits
  28. 27 Nov, 2012 1 commit
  29. 18 Oct, 2012 1 commit
  30. 25 Aug, 2012 1 commit