1. 11 Apr, 2016 1 commit
    • diff_tform: fix potential NULL pointer access · 851c51ab
      When the user passes in a diff which has no repository associated
      we may call `git_config__get_int_force` with a NULL-pointer
      configuration. Even though `git_config__get_int_force` is
      designed to swallow errors, it is not intended to be called with
      a NULL pointer configuration.
      
      Fix the issue by only calling `git_config__get_int_force` only
      when configuration could be retrieved from the repository.
      Patrick Steinhardt committed
  2. 23 Feb, 2016 1 commit
    • diff_tform: fix potential NULL pointer access · 32f07984
      The `normalize_find_opts` function in theory allows for the
      incoming diff to have no repository. When the caller does not
      pass in diff find options or if the GIT_DIFF_FIND_BY_CONFIG value
      is set, though, we try to derive the configuration from the
      diff's repository configuration without first verifying that the
      repository is actually set to a non-NULL value.
      
      Fix this issue by explicitly checking if the repository is set
      and if it is not, fall back to a default value of
      GIT_DIFF_FIND_RENAMES.
      Patrick Steinhardt committed
  3. 28 Oct, 2015 1 commit
  4. 23 Jun, 2015 4 commits
  5. 10 Jun, 2015 1 commit
  6. 30 Mar, 2015 1 commit
  7. 03 Mar, 2015 1 commit
  8. 13 Feb, 2015 2 commits
  9. 14 Jan, 2015 1 commit
  10. 27 Oct, 2014 1 commit
  11. 01 Oct, 2014 1 commit
  12. 20 May, 2014 1 commit
  13. 02 May, 2014 1 commit
  14. 24 Feb, 2014 2 commits
  15. 25 Jan, 2014 1 commit
  16. 22 Jan, 2014 1 commit
  17. 12 Dec, 2013 2 commits
  18. 11 Dec, 2013 3 commits
    • Add git_vector_free_all · fcd324c6
      There are a lot of places that we call git__free on each item in
      a vector and then call git_vector_free on the vector itself.  This
      just wraps that up into one convenient helper function.
      Russell Belfer committed
    • Add config read fns with controlled error behavior · 9f77b3f6
      This adds `git_config__lookup_entry` which will look up a key in
      a config and return either the entry or NULL if the key was not
      present.  Optionally, it can either suppress all errors or can
      return them (although not finding the key is not an error for this
      function).  Unlike other accessors, this does not normalize the
      config key string, so it must only be used when the key is known
      to be in normalized form (i.e. all lower-case before the first dot
      and after the last dot, with no invalid characters).
      
      This also adds three high-level helper functions to look up config
      values with no errors and a fallback value.  The three functions
      are for string, bool, and int values, and will resort to the
      fallback value for any error that arises.  They are:
      
      * `git_config__get_string_force`
      * `git_config__get_bool_force`
      * `git_config__get_int_force`
      
      None of them normalize the config `key` either, so they can only
      be used for internal cases where the key is known to be in normal
      format.
      Russell Belfer committed
    • Check version earlier · 5a52d6be
      Ben Straub committed
  19. 06 Dec, 2013 1 commit
  20. 05 Dec, 2013 2 commits
  21. 02 Dec, 2013 3 commits
  22. 01 Nov, 2013 2 commits
    • More tests and fixed for merging reversed diffs · e7c85120
      There were a lot more cases to deal with to make sure that our
      merged (i.e. workdir-to-tree-to-index) diffs were matching the
      output of core Git.
      Russell Belfer committed
    • Fix some of the glaring errors in GIT_DIFF_REVERSE · 3940310e
      These changes fix the basic problem with GIT_DIFF_REVERSE being
      broken for text diffs.  The reversed diff entries were getting
      added to the git_diff correctly, but some of the metadata was kept
      incorrectly in a way that prevented the text diffs from being
      generated correctly.  Once I fixed that, it became clear that it
      was not possible to merge reversed diffs correctly.  This has a
      first pass at fixing that problem.  We probably need more tests
      to make sure that is really fixed thoroughly.
      Russell Belfer committed
  23. 21 Oct, 2013 1 commit
  24. 15 Oct, 2013 1 commit
    • Diff API cleanup · 10672e3e
      This lays groundwork for separating formatting options from diff
      creation options.  This groups the formatting flags separately
      from the diff list creation flags and reorders the options.  This
      also tweaks some APIs to further separate code that uses patches
      from code that just looks at git_diffs.
      Russell Belfer committed
  25. 11 Oct, 2013 1 commit
  26. 28 Aug, 2013 1 commit
  27. 22 Aug, 2013 1 commit
  28. 04 Aug, 2013 1 commit
    • Update rename src map for any split src · 7edb74d3
      When using a rename source that is actually a to-be-split record,
      we have to update the best-fit mapping data in both the case where
      the target is also a split record and the case where the target
      is a simple added record.  Before this commit, we were only doing
      the update when the target was itself a split record (and even in
      that case, the test was slightly wrong).
      Russell Belfer committed