Project

General

Profile

Actions
Copy link

Defect #3567

closed

Sorting for changesets might go wrong on Mercurial repos

Added by Ammler _ almost 15 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Toshi MARUYAMA
Category:
SCM
Target version:
1.1.0
Start date:
2009-06-30
Due date:
% Done:

100%

Estimated time:
Resolution:
Fixed
Affected version:

Description

The DVCS Mercurial allows to commit changesets with configureable, i.e. with "hg ci -d "2222-10-20...", then the next changeset could have a earlier date. Of course, ususally it shouldn't happen, but it can, maybe only seconds but it does. :-)

So the sorting depend on revision number for Mercurial, Git doesn't have numbers (in Redmine), so it can't be used as general setting.

I don't know, if it's a bug or a feature request, feel free to decide that self. ;-)

Examples from 2 repos (the "bad" version is r137):

Files

Download all files
redmine_hg_sorting.png (22 KB) redmine_hg_sorting.png Ammler _, 2009-07-01 13:18
redmine-sort-by-date.png (12.8 KB) redmine-sort-by-date.png Toshi MARUYAMA, 2010-03-07 12:58
redmine-sort-by-revno.png (14.3 KB) redmine-sort-by-revno.png Toshi MARUYAMA, 2010-03-07 12:58
hg-order-before.png (45.9 KB) hg-order-before.png Toshi MARUYAMA, 2010-10-08 12:27
hg-order-after.png (50.7 KB) hg-order-after.png Toshi MARUYAMA, 2010-10-08 12:27

Related issues

Related to Redmine - Defect #3449: Redmine Takes Too Long On Large Mercurial RepositoryClosedToshi MARUYAMA2009-06-05

Actions
Actions
Copy link

Also available in: Atom PDF