Vote #63522
完了Associated revisions are displayed in wrong order for Git, Mercurial (SHA-1 DVCSs)
0%
説明
Associated revisions are currently sorted by revision name, in ascending order. (@source:trunk/app/models/issue.rb@1594#L31@) However, certain SCMs don't use sequential numeric values (for instance: Git, Mercurial and Monotone use SHA-1 hashes), and the commits appear possibly in the wrong order for them.
This trivial patch tries to order first by the @committed_on@ field, leaving the @revision@ as a secondary sorting column.
journals
You're right. This sort order wasn't updated when the revision field was changed from numeric to string.
Fixed in r1596.
has_and_belongs_to_many :changesets, :order => "#{Changeset.table_name}.committed_on ASC, #{Changeset.table_name}.id ASC"
--------------------------------------------------------------------------------
> has_and_belongs_to_many :changesets, :order => "#{Changeset.table_name}.committed_on ASC, #{Changeset.table_name}.id ASC"
can I suggest this would be nicer (or at least optional) to be DESC rather than ASC so the latest revision is the topmost, as per activity and most other lists throughout the interface? that's how I've set it in mine.
--------------------------------------------------------------------------------
Changed in r2519. Changsets are now sorted in the same order as the comments (which is based on a user preference).
--------------------------------------------------------------------------------