1. 01 Dec, 2015 1 commit
  2. 20 Nov, 2015 1 commit
  3. 03 Nov, 2015 1 commit
  4. 02 Nov, 2015 1 commit
  5. 21 Oct, 2015 1 commit
  6. 25 Sep, 2015 1 commit
    • Fix binary diffs · e4b2b919
      git expects an empty line after the binary data:
      
      literal X
      ...binary data...
      <empty_line>
      
      The last literal block of the generated patches were not containing the required empty line. Example:
      
      	diff --git a/binary_file b/binary_file
      	index 3f1b3f9098131cfecea4a50ff8afab349ea66d22..86e5c1008b5ce635d3e3fffa4434c5eccd8f00b6 100644
      	GIT binary patch
      	literal 8
      	Pc${NM&PdElPvrst3ey5{
      
      	literal 6
      	Nc${NM%g@i}0ssZ|0lokL
      	diff --git a/binary_file2 b/binary_file2
      	index 31be99be19470da4af5b28b21e27896a2f2f9ee2..86e5c1008b5ce635d3e3fffa4434c5eccd8f00b6 100644
      	GIT binary patch
      	literal 8
      	Pc${NM&PdElPvrst3ey5{
      
      	literal 13
      	Sc${NMEKbZyOexL+Qd|HZV+4u-
      
      git apply of that diff results in:
      
      	error: corrupt binary patch at line 9: diff --git a/binary_file2 b/binary_file2
      	fatal: patch with only garbage at line 10
      
      The proper formating is:
      
      	diff --git a/binary_file b/binary_file
      	index 3f1b3f9098131cfecea4a50ff8afab349ea66d22..86e5c1008b5ce635d3e3fffa4434c5eccd8f00b6 100644
      	GIT binary patch
      	literal 8
      	Pc${NM&PdElPvrst3ey5{
      
      	literal 6
      	Nc${NM%g@i}0ssZ|0lokL
      	diff --git a/binary_file2 b/binary_file2
      	index 31be99be19470da4af5b28b21e27896a2f2f9ee2..86e5c1008b5ce635d3e3fffa4434c5eccd8f00b6 100644
      	GIT binary patch
      	literal 8
      	Pc${NM&PdElPvrst3ey5{
      
      	literal 13
      	Sc${NMEKbZyOexL+Qd|HZV+4u-
      Guille -bisho- committed
  7. 12 Sep, 2015 1 commit
  8. 31 Aug, 2015 1 commit
    • iterator: saner pathlist matching for idx iterator · d53c8880
      Some nicer refactoring for index iteration walks.
      
      The index iterator doesn't binary search through the pathlist space,
      since it lacks directory entries, and would have to binary search
      each index entry and all its parents (eg, when presented with an index
      entry of `foo/bar/file.c`, you would have to look in the pathlist for
      `foo/bar/file.c`, `foo/bar` and `foo`).  Since the index entries and the
      pathlist are both nicely sorted, we walk the index entries in lockstep
      with the pathlist like we do for other iteration/diff/merge walks.
      Edward Thomson committed
  9. 30 Aug, 2015 1 commit
  10. 29 Aug, 2015 1 commit
  11. 28 Aug, 2015 1 commit
  12. 15 Aug, 2015 1 commit
  13. 30 Jun, 2015 1 commit
  14. 26 Jun, 2015 4 commits
  15. 25 Jun, 2015 1 commit
  16. 24 Jun, 2015 2 commits
  17. 23 Jun, 2015 2 commits
  18. 22 Jun, 2015 6 commits
  19. 16 Jun, 2015 2 commits
    • tests: tick the index when we count OID calculations · e44abe16
      These tests want to test that we don't recalculate entries which match
      the index already. This is however something we force when truncating
      racily-clean entries.
      
      Tick the index forward as we know that we don't perform the
      modifications which the racily-clean code is trying to avoid.
      Carlos Martín Nieto committed
    • diff: add failing test for racy-git in the index · 77596fcf
      We update the index and then immediately change the contents of the
      file. This makes the diff think there are no changes, as the timestamp
      of the file agrees with the cached data. This is however a bug, as the
      file has obviously changed contents.
      
      The test is a bit fragile, as it assumes that the index writing and the
      following modification of the file happen in the same second, but it's
      enough to show the issue.
      Carlos Martín Nieto committed
  20. 15 Jun, 2015 1 commit
  21. 12 Jun, 2015 3 commits
  22. 02 Jun, 2015 1 commit
  23. 28 May, 2015 2 commits
  24. 01 May, 2015 1 commit
  25. 04 Mar, 2015 1 commit
  26. 03 Mar, 2015 1 commit