Files
gitlabhq/app/models
Sean McGivern 27fdd3fe50 Maintain commit order in MRs
`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.
2016-05-18 17:14:55 +01:00
..
2011-10-09 00:36:38 +03:00
2016-05-14 18:23:31 -05:00
2016-04-28 21:28:39 +02:00
2016-03-06 23:07:19 -05:00
2016-03-29 12:19:09 +01:00
2015-12-18 14:19:48 -06:00
2016-05-16 10:25:24 +01:00
2016-05-13 17:55:42 -05:00
2016-05-16 14:56:32 -03:00