1. 09 Apr, 2015 1 commit
  2. 07 Apr, 2015 1 commit
  3. 02 Apr, 2015 1 commit
  4. 01 Apr, 2015 1 commit
  5. 31 Mar, 2015 2 commits
  6. 30 Mar, 2015 3 commits
  7. 27 Mar, 2015 7 commits
  8. 26 Mar, 2015 2 commits
  9. 25 Mar, 2015 4 commits
  10. 23 Mar, 2015 6 commits
  11. 22 Mar, 2015 1 commit
  12. 18 Mar, 2015 2 commits
  13. 17 Mar, 2015 1 commit
  14. 16 Mar, 2015 2 commits
  15. 13 Mar, 2015 3 commits
  16. 12 Mar, 2015 2 commits
  17. 11 Mar, 2015 1 commit
    • Kirill Smelkov's avatar
      Revert "BigFile: Fixes, Tests and on-server Append support" · 4f3bb0c9
      Kirill Smelkov authored
      This reverts commit 193f5cdd, reversing
      changes made to 4ee61a23.
      
      Jean-Paul suggested we first better further review our code review / merging
      procedures and use e.g. this particular merge request as a basis for that.
      
      Thus I'm reverting this merge, so people could study and re-merge it
      "properly".
      
      ~~~~
      
      Please note: I could potentially rewrite master history so that there
      would be a no merge commit at all, as e.g. my branch was not so far ever
      merged at all. In contrast to draft branches, that is however a not good
      practice to rebase, and thus rewrite, master history - what has been
      committed is committed and we only continue.
      
      So later to re-merge my branch, if it will not be changed, we'll need to
      first revert this revert (see [1] for rationale), or alternatively I
      could re-prepare my patches with different sha1 ids and they will merge
      again the "usual way".
      
      [1] http://git-scm.com/docs/howto/revert-a-faulty-merge.html
      4f3bb0c9