1. 29 Jun, 2016 1 commit
  2. 03 Jun, 2016 2 commits
  3. 01 Jun, 2016 1 commit
  4. 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
  5. 14 May, 2016 1 commit
  6. 09 May, 2016 1 commit
  7. 06 May, 2016 1 commit
  8. 19 Apr, 2016 1 commit
  9. 12 Apr, 2016 1 commit
  10. 04 Mar, 2016 1 commit
  11. 03 Mar, 2016 1 commit
  12. 27 Jan, 2016 1 commit
  13. 20 Jan, 2016 1 commit
  14. 13 Nov, 2015 1 commit
  15. 20 Oct, 2015 1 commit
  16. 16 Oct, 2015 1 commit
  17. 03 Oct, 2015 1 commit
  18. 25 Sep, 2015 1 commit
  19. 11 Aug, 2015 3 commits
  20. 07 Aug, 2015 1 commit
  21. 16 Jul, 2015 1 commit
  22. 15 Jul, 2015 3 commits
  23. 24 Apr, 2015 1 commit
  24. 05 Feb, 2015 1 commit
  25. 10 Oct, 2014 1 commit
  26. 25 Aug, 2014 1 commit
  27. 29 Jul, 2014 1 commit
  28. 26 Jun, 2014 1 commit
  29. 07 May, 2014 1 commit
  30. 14 Apr, 2014 1 commit
  31. 11 Apr, 2014 1 commit
  32. 09 Apr, 2014 1 commit
  33. 27 Feb, 2014 1 commit
  34. 12 Feb, 2014 1 commit
  35. 22 Jan, 2014 1 commit