1. 28 Apr, 2015 6 commits
  2. 24 Apr, 2015 1 commit
  3. 23 Apr, 2015 10 commits
  4. 21 Apr, 2015 2 commits
    • git_config_delete: search until last section. · 9a810c5e
      If git_config_delete is to work properly in the presence of duplicate section
      headers, it cannot stop searching at the end of the first matching section, as
      there may be another matching section later.
      When config_write is used for deletion (value = NULL), it may only terminate
      when the desired key is found or there are no sections left to parse.
      Ryan Roden-Corrent committed
    • Fix index-adding functions to know when to trust filemodes. · d3282680
      The idea...sometimes, a filemode is user-specified via an
      explicit git_index_entry.  In this case, believe the user, always.
      
      Sometimes, it is instead built up by statting the file system.  In
      those cases, go with the existing logic we have to determine
      whether the file system supports all filemodes and symlinks, and
      make the best guess.
      
      On file systems which have full filemode and symlink support, this
      commit should make no difference.  On others (most notably Windows),
      this will fix problems things like:
      * git_index_add and git_index_add_frombuffer() should be believed.
      * As a consequence, git_checkout_tree should make the filemodes in
      the index match the ones in the tree.
      * And diffs with GIT_DIFF_UPDATE_INDEX don't write the wrong filemodes.
      * And merges, and probably other downstream stuff now fixed, too.
      
      This makes my previous changes to checkout.c unnecessary,
      so they are now reverted.
      
      Also, added a test for index_entry permissions from git_index_add
      and git_index_add_frombuffer, both of which failed before these changes.
      John Fultz committed
  5. 20 Apr, 2015 8 commits
  6. 18 Apr, 2015 1 commit
  7. 17 Apr, 2015 4 commits
  8. 16 Apr, 2015 1 commit
  9. 15 Apr, 2015 4 commits
  10. 14 Apr, 2015 1 commit
    • revwalk: detect when we're out of interesting commits · a0541695
      When walking backwards and marking parents uninteresting, make sure we
      detect when the list of commits we have left has run out of
      uninteresting commits so we can stop marking commits as
      uninteresting. Failing to do so can mean that we walk the whole history
      marking everything uninteresting, which eats up time, CPU and IO for
      with useless work.
      
      While pre-marking does look for this, we still need to check during the
      main traversal as there are setups for which pre-marking does not leave
      enough information in the commits. This can happen if we push a commit
      and hide its parent.
      Carlos Martín Nieto committed
  11. 12 Apr, 2015 1 commit
  12. 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