| @@ -92,6 +92,17 class Repository::Git < Repository | |||||
| 92 | options = {:report_last_commit => extra_report_last_commit}) |
|
92 | options = {:report_last_commit => extra_report_last_commit}) | |
| 93 | end |
|
93 | end | |
| 94 |
|
94 | |||
|
|
95 | # With SCMs that have a sequential commit numbering, | |||
|
|
96 | # such as Subversion and Mercurial, | |||
|
|
97 | # Redmine is able to be clever and only fetch changesets | |||
|
|
98 | # going forward from the most recent one it knows about. | |||
|
|
99 | # | |||
|
|
100 | # However, Git does not have a sequential commit numbering. | |||
|
|
101 | # | |||
|
|
102 | # In order to fetch only new adding revisions, | |||
|
|
103 | # Redmine need to parse revisions per branch. | |||
|
|
104 | # Branch "last_scmid" is for this requirement. | |||
|
|
105 | # | |||
| 95 | # In Git and Mercurial, revisions are not in date order. |
|
106 | # In Git and Mercurial, revisions are not in date order. | |
| 96 | # Redmine Mercurial fixed issues. |
|
107 | # Redmine Mercurial fixed issues. | |
| 97 | # * Redmine Takes Too Long On Large Mercurial Repository |
|
108 | # * Redmine Takes Too Long On Large Mercurial Repository | |
General Comments 0
You need to be logged in to leave comments.
Login now