1. 23 Feb, 2022 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. 07 Feb, 2020 1 commit
  4. 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
  5. 10 Jun, 2018 1 commit
  6. 11 Mar, 2016 1 commit
  7. 07 Mar, 2016 1 commit
  8. 25 Feb, 2016 1 commit
    • nsec: update staging test for GIT_USE_NSECS · a4c55069
      The index::nsec::staging_maintains_other_nanos test was created to
      ensure that when we stage an entry when GIT_USE_NSECS is *unset* that
      we truncate the index entry and do not persist the (old, invalid)
      nanosec values.  Ensure that when GIT_USE_NSECS is *set* that we do
      not do that, and actually write the correct nanosecond values.
      Edward Thomson committed
  9. 22 Oct, 2015 1 commit
    • index: test that we round-trip nsecs · 99a09f7f
      Test that nanoseconds are round-tripped correctly when we read
      an index file that contains them.  We should, however, ignore them
      because we don't understand them, and any new entries in the index
      should contain a `0` nsecs field, while existing preserving entries.
      Edward Thomson committed