1. 29 Dec, 2016 1 commit
  2. 22 Oct, 2014 1 commit
    • tree-cache: correct the entry_count calculation · bb0757d5
      The entry_count field is the amount of index entries covered by a
      particular cache entry, that is how many files are there (recursively)
      under a particular directory.
      
      The current code that attemps to do this is severely defincient and is
      trying to count the amount of children, which always comes up to zero.
      
      We don't even need to recount, since we have the information during the
      cache creation. We can take that number and keep it, as we only ever
      invalidate or replace.
      Carlos Martín Nieto committed
  3. 13 Oct, 2014 1 commit
  4. 10 Oct, 2014 6 commits
  5. 17 Apr, 2014 1 commit
    • Minor tree cache speedups · 1fa17b5c
      While I was looking at the conflict cleanup code, I looked over at
      the tree cache code, since we clear the tree cache for each entry
      that gets removed and there is some redundancy there.  I made some
      small tweaks to avoid extra calls to strchr and strlen in a few
      circumstances.
      Russell Belfer committed
  6. 19 Nov, 2013 4 commits
  7. 08 Jan, 2013 1 commit
  8. 12 Dec, 2012 1 commit
    • tree cache: loosen negative entry count check · 08f3d6ca
      While C Git has been writing entry count -1 (ie. never other negative
      numbers) as invalid since day 1, it accepts all negative entry counts
      as invalid. JGit follows the same rule. libgit2 should also follow, or
      the index that works with C Git or JGit may someday be rejected by
      libgit2.
      
      Other reimplementations like dulwich and grit have not bothered with
      parsing or writing tree cache.
      Nguyễn Thái Ngọc Duy committed
  9. 07 Jun, 2012 1 commit
  10. 03 May, 2012 1 commit
  11. 23 Apr, 2012 1 commit
  12. 20 Apr, 2012 1 commit
  13. 13 Feb, 2012 1 commit
  14. 29 Oct, 2011 1 commit
  15. 27 Sep, 2011 5 commits