summaryrefslogtreecommitdiffstats
path: root/app/models
diff options
context:
space:
mode:
authorToshi MARUYAMA <marutosijp2@yahoo.co.jp>2011-05-04 23:36:57 +0000
committerToshi MARUYAMA <marutosijp2@yahoo.co.jp>2011-05-04 23:36:57 +0000
commita7c178f6a6013b4625fb11147648d57b9a257260 (patch)
tree768a3aba09f0831d171584b8c36282fc16e81dc5 /app/models
parent19a9cba214d8ae72d1200ce911438683e9c97159 (diff)
downloadredmine-a7c178f6a6013b4625fb11147648d57b9a257260.tar.gz
redmine-a7c178f6a6013b4625fb11147648d57b9a257260.zip
scm: git: rearrange fetch_changesets() comment.
git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5643 e93f8b46-1217-0410-a6f0-8f06a7374b81
Diffstat (limited to 'app/models')
-rw-r--r--app/models/repository/git.rb10
1 files changed, 7 insertions, 3 deletions
diff --git a/app/models/repository/git.rb b/app/models/repository/git.rb
index 473c3535d..198e39dc9 100644
--- a/app/models/repository/git.rb
+++ b/app/models/repository/git.rb
@@ -72,10 +72,14 @@ class Repository::Git < Repository
# 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
- # 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
- # the entire log. Since it's way too slow for large repositories, we only
- # parse 1 week before the last known commit.
+ # the entire log.
+ #
+ # 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
# before fetching changesets (eg. for offline resync)
def fetch_changesets