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