| @@ -89,18 +89,19 class Repository::Git < Repository | |||
|
|
89 | 89 | end |
|
|
90 | 90 | |
|
|
91 | 91 | # In Git and Mercurial, revisions are not in date order. |
|
|
92 | # Mercurial fixed issues. | |
|
|
92 | # Redmine Mercurial fixed issues. | |
|
|
93 | 93 | # * Redmine Takes Too Long On Large Mercurial Repository |
|
|
94 | 94 | # http://www.redmine.org/issues/3449 |
|
|
95 | 95 | # * Sorting for changesets might go wrong on Mercurial repos |
|
|
96 | 96 | # http://www.redmine.org/issues/3567 |
|
|
97 | # | |
|
|
97 | 98 | # Database revision column is text, so Redmine can not sort by revision. |
|
|
98 | 99 | # Mercurial has revision number, and revision number guarantees revision order. |
|
|
99 | # Mercurial adapter uses "hg log -r 0:tip --limit 10" | |
|
|
100 | # to get limited revisions from old to new. | |
|
|
101 | # And Mercurial model stored revisions ordered by database id in database. | |
|
|
102 | # So, Mercurial can use correct order revisions. | |
|
|
100 | # Redmine Mercurial model stored revisions ordered by database id to database. | |
|
|
101 | # So, Redmine Mercurial model can use correct ordering revisions. | |
|
|
103 | 102 | # |
|
|
103 | # Redmine Mercurial adapter uses "hg log -r 0:tip --limit 10" | |
|
|
104 | # to get limited revisions from old to new. | |
|
|
104 | 105 | # But, Git 1.7.3.4 does not support --reverse with -n or --skip. |
|
|
105 | 106 | # |
|
|
106 | 107 | # The repository can still be fully reloaded by calling #clear_changesets |
General Comments 0
You need to be logged in to leave comments.
Login now