summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorToshi MARUYAMA <marutosijp2@yahoo.co.jp>2011-05-04 23:42:58 +0000
committerToshi MARUYAMA <marutosijp2@yahoo.co.jp>2011-05-04 23:42:58 +0000
commit240254b1a37098fbad9ee68bfe9de769145673a9 (patch)
tree6627370c44fd18cd941ec871a4ea3f124c257278
parent95f3c336d5f3aba4ee2dfeb913dc8aba6fa08c69 (diff)
downloadredmine-240254b1a37098fbad9ee68bfe9de769145673a9.tar.gz
redmine-240254b1a37098fbad9ee68bfe9de769145673a9.zip
Merged r5643 from trunk.
scm: git: rearrange fetch_changesets() comment. git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/branches/1.1-stable@5645 e93f8b46-1217-0410-a6f0-8f06a7374b81
-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 9349f3c11..c90862995 100644
--- a/app/models/repository/git.rb
+++ b/app/models/repository/git.rb
@@ -49,10 +49,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