kolan
/
Redmine
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

scm: git: rearrange fetch_changesets() comment. 

git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5643 e93f8b46-1217-0410-a6f0-8f06a7374b81
This commit is contained in:
Toshi MARUYAMA 2011-05-04 23:36:57 +00:00
parent 19a9cba214
commit a7c178f6a6
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
app/models/repository/git.rb
View File

@ -72,10 +72,14 @@ class Repository::Git < Repository
# With SCM's that have a sequential commit numbering, redmine is able to be # With SCM's that have a sequential commit numbering, redmine is able to be
# clever and only fetch changesets going forward from the most recent one # clever and only fetch changesets going forward from the most recent one
# it knows about. However, with git, you never know if people have merged # it knows about.
# However, with git, you never know if people have merged
# commits into the middle of the repository history, so we should parse # commits into the middle of the repository history, so we should parse
# the entire log. Since it's way too slow for large repositories, we only # the entire log.
# parse 1 week before the last known commit. #
# Since it's way too slow for large repositories,
# we only parse 1 week before the last known commit.
#
# The repository can still be fully reloaded by calling #clear_changesets # The repository can still be fully reloaded by calling #clear_changesets
# before fetching changesets (eg. for offline resync) # before fetching changesets (eg. for offline resync)
def fetch_changesets def fetch_changesets