| @@ -72,10 +72,14 class Repository::Git < Repository | |||||
| 72 |
|
72 | |||
| 73 | # With SCM's that have a sequential commit numbering, redmine is able to be |
|
73 | # With SCM's that have a sequential commit numbering, redmine is able to be | |
| 74 | # clever and only fetch changesets going forward from the most recent one |
|
74 | # clever and only fetch changesets going forward from the most recent one | |
| 75 | # it knows about. However, with git, you never know if people have merged |
|
75 | # it knows about. | |
|
|
76 | # However, with git, you never know if people have merged | |||
| 76 | # commits into the middle of the repository history, so we should parse |
|
77 | # commits into the middle of the repository history, so we should parse | |
| 77 | # the entire log. Since it's way too slow for large repositories, we only |
|
78 | # the entire log. | |
| 78 | # parse 1 week before the last known commit. |
|
79 | # | |
|
|
80 | # Since it's way too slow for large repositories, | |||
|
|
81 | # we only parse 1 week before the last known commit. | |||
|
|
82 | # | |||
| 79 | # The repository can still be fully reloaded by calling #clear_changesets |
|
83 | # The repository can still be fully reloaded by calling #clear_changesets | |
| 80 | # before fetching changesets (eg. for offline resync) |
|
84 | # before fetching changesets (eg. for offline resync) | |
| 81 | def fetch_changesets |
|
85 | def fetch_changesets | |
General Comments 0
You need to be logged in to leave comments.
Login now