1. 24 Nov, 2015 2 commits
  2. 17 Nov, 2015 1 commit
  3. 30 Oct, 2015 1 commit
  4. 21 Oct, 2015 1 commit
  5. 18 Sep, 2015 1 commit
  6. 17 Sep, 2015 1 commit
    • git_futils_mkdir_*: make a relative-to-base mkdir · ac2fba0e
      Untangle git_futils_mkdir from git_futils_mkdir_ext - the latter
      assumes that we own everything beneath the base, as if it were
      being called with a base of the repository or working directory,
      and is tailored towards checkout and ensuring that there is no
      bogosity beneath the base that must be cleaned up.
      
      This is (at best) slow and (at worst) unsafe in the larger context
      of a filesystem where we do not own things and cannot do things like
      unlink symlinks that are in our way.
      Edward Thomson committed
  7. 13 Sep, 2015 1 commit
  8. 12 Aug, 2015 3 commits
  9. 04 May, 2015 7 commits
  10. 23 Apr, 2015 2 commits
  11. 21 Apr, 2015 2 commits
  12. 20 Apr, 2015 2 commits
  13. 10 Apr, 2015 1 commit
    • Fix checking of return value for regcomp. · 129022ee
      The regcomp function returns a non-zero value if compilation of
      a regular expression fails. In most places we only check for
      negative values, but positive values indicate an error, as well.
      Fix this tree-wide, fixing a segmentation fault when calling
      git_config_iterator_glob_new with an invalid regexp.
      Patrick Steinhardt committed
  14. 03 Mar, 2015 2 commits
    • config: borrow refcounted references · 9a97f49e
      This changes the get_entry() method to return a refcounted version of
      the config entry, which you have to free when you're done.
      
      This allows us to avoid freeing the memory in which the entry is stored
      on a refresh, which may happen at any time for a live config.
      
      For this reason, get_string() has been forbidden on live configs and a
      new function get_string_buf() has been added, which stores the string in
      a git_buf which the user then owns.
      
      The functions which parse the string value takea advantage of the
      borrowing to parse safely and then release the entry.
      Carlos Martín Nieto committed
  15. 12 Feb, 2015 1 commit
  16. 14 Jan, 2015 1 commit
  17. 10 Dec, 2014 1 commit
  18. 03 Nov, 2014 1 commit
  19. 01 Nov, 2014 1 commit
  20. 27 Oct, 2014 1 commit
  21. 23 Oct, 2014 3 commits
  22. 04 Oct, 2014 1 commit
  23. 09 Aug, 2014 1 commit
    • config: a multiline var can start immediately · 9dac1f95
      In the check for multiline, we traverse the backslashes from the end
      backwards and int the end assert that we haven't gone past the beginning
      of the line. We make sure of this in the loop condition, but we also
      check in the return value.
      
      However, for certain configurations, a line in a multiline variable
      might be empty to aid formatting. In that case, 'end' == 'start', since
      we ended up looking at the first char which made it a multiline.
      
      There is no need for the (end > start) check in the return, since the
      loop guarantees we won't go further back than the first char in the
      line, and we do accept the first char to be the final backslash.
      
      This fixes #2483.
      Carlos Martín Nieto committed
  24. 16 Jul, 2014 1 commit
  25. 15 May, 2014 1 commit
    • Better search path sandboxing · 8487e237
      There are a number of tests that modify the global or system
      search paths during the tests.  This adds a helper function to
      make it easier to restore those paths and makes sure that they
      are getting restored in a manner that preserves test isolation.
      Russell Belfer committed