1. 11 Jul, 2016 1 commit
  2. 08 Jul, 2016 2 commits
  3. 07 Jul, 2016 6 commits
  4. 04 Jul, 2016 1 commit
  5. 29 Jun, 2016 1 commit
  6. 03 Jun, 2016 2 commits
  7. 01 Jun, 2016 1 commit
  8. 18 May, 2016 1 commit
    • Sean McGivern's avatar
      Maintain commit order in MRs · 27fdd3fe
      Sean McGivern authored
      `Gitlab::Git::Compare` will already have the correct order; sorting in
      Ruby can only ruin that. (The correct order being the same as `git log`
      - reverse chronological while maintaining the commit graph.)
      
      As an example, imagine a branch where someone has their system clock set
      wrong for some of the commits. Not only will those commits be in the
      wrong order - which is maybe reasonable - but sorting in Ruby can also
      put commits with the same timestamp out of order, as Ruby's sorting
      isn't stable.
      27fdd3fe
  9. 14 May, 2016 1 commit
  10. 09 May, 2016 1 commit
  11. 06 May, 2016 1 commit
  12. 19 Apr, 2016 1 commit
  13. 12 Apr, 2016 1 commit
  14. 04 Mar, 2016 1 commit
  15. 03 Mar, 2016 1 commit
  16. 27 Jan, 2016 1 commit
  17. 20 Jan, 2016 1 commit
  18. 13 Nov, 2015 1 commit
  19. 20 Oct, 2015 1 commit
  20. 16 Oct, 2015 1 commit
  21. 03 Oct, 2015 1 commit
  22. 25 Sep, 2015 1 commit
  23. 11 Aug, 2015 3 commits
  24. 07 Aug, 2015 1 commit
  25. 16 Jul, 2015 1 commit
  26. 15 Jul, 2015 3 commits
  27. 24 Apr, 2015 1 commit
  28. 05 Feb, 2015 1 commit
  29. 10 Oct, 2014 1 commit