From a7c178f6a6013b4625fb11147648d57b9a257260 Mon Sep 17 00:00:00 2001 From: Toshi MARUYAMA Date: Wed, 4 May 2011 23:36:57 +0000 Subject: [PATCH] scm: git: rearrange fetch_changesets() comment. git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@5643 e93f8b46-1217-0410-a6f0-8f06a7374b81 --- app/models/repository/git.rb | 10 +++++++--- 1 file 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