Sorting for changesets might go wrong on Mercurial repos
|Assignee:||Toshi MARUYAMA||% Done:|
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):
#6 Updated by Yuya Nishihara about 10 years ago
It seems we can simply use
ORDER BY id. At least, both Subversion and Mercurial insert changesets from earliest.