diff options
author | Toshi MARUYAMA <marutosijp2@yahoo.co.jp> | 2011-10-27 00:41:37 +0000 |
---|---|---|
committer | Toshi MARUYAMA <marutosijp2@yahoo.co.jp> | 2011-10-27 00:41:37 +0000 |
commit | 8da22803befa91ed92922393ee0a1342b2b0e24e (patch) | |
tree | 41a0efd74a1b67361aaa50525cfc2d09d531d994 | |
parent | 83ab216d705ec367aed89dcbcf1a602e1f2c750e (diff) | |
download | redmine-8da22803befa91ed92922393ee0a1342b2b0e24e.tar.gz redmine-8da22803befa91ed92922393ee0a1342b2b0e24e.zip |
Merged r7658 from trunk
scm: git: recovery and improve comments of fetching from 1.1
about harmful influence that git does not have the revision number.
git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/branches/1.2-stable@7659 e93f8b46-1217-0410-a6f0-8f06a7374b81
-rw-r--r-- | app/models/repository/git.rb | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/app/models/repository/git.rb b/app/models/repository/git.rb index 7d96d002c..18232ef5a 100644 --- a/app/models/repository/git.rb +++ b/app/models/repository/git.rb @@ -92,6 +92,17 @@ class Repository::Git < Repository options = {:report_last_commit => extra_report_last_commit}) end + # With SCMs that have a sequential commit numbering, + # such as Subversion and Mercurial, + # Redmine is able to be clever and only fetch changesets + # going forward from the most recent one it knows about. + # + # However, Git does not have a sequential commit numbering. + # + # In order to fetch only new adding revisions, + # Redmine need to parse revisions per branch. + # Branch "last_scmid" is for this requirement. + # # In Git and Mercurial, revisions are not in date order. # Redmine Mercurial fixed issues. # * Redmine Takes Too Long On Large Mercurial Repository |